Forums
April 29, 2024, 02:54 PM

Author Topic: Update your WormNAT2!  (Read 8938 times)

0 Members and 1 Guest are viewing this topic.

Offline Sensei

Re: Update your WormNAT2!
« Reply #30 on: September 22, 2015, 11:57 PM »
Ok Cyber, I upgraded it again so you can find bugs related to this new version of wormnat2.

Earlier played Big RR with KungPow and in the middle of the game got chat message "skipped packet" but there was no any disconnections.. (search replay @7:39)

Then it happened again few games after, while we were playing Aerial. Only this time I dropped after message.
(search replay @8:27)


Offline CyberShadow

  • W:A maintainer
  • Full Member
  • *****

  • Moldova Moldova
  • Posts: 173
    • View Profile
    • Homepage
Re: Update your WormNAT2!
« Reply #31 on: September 23, 2015, 12:53 AM »
`KungPow` still has wkPackets.dll, he needs to delete it (whether he uses WormNAT2 or not, but if he does, he needs to update).

Offline philie

Re: Update your WormNAT2!
« Reply #32 on: September 23, 2015, 06:14 PM »
i'm using wheat with new wormnat: except for a few error messages everything seems to work fine.
i just press enter 3 times before hosting xD

Offline Almog

Re: Update your WormNAT2!
« Reply #33 on: November 06, 2015, 07:44 PM »
hey I'm getting that error:

Offline Almog

Re: Update your WormNAT2!
« Reply #34 on: November 06, 2015, 07:48 PM »
hey I'm getting that error:
[attachment=1]

well. I disabled workmit modules from W:A advanced options, and that error stopped (obviously), but for some reason I can still host with Great Snopper :o

Offline TheWalrus

Re: Update your WormNAT2!
« Reply #35 on: November 06, 2015, 07:48 PM »
hey I'm getting that error:
[attachment=1]
Same, just been ignoring it though because I can still host.  You having any problems hosting?

Offline aik

Re: Update your WormNAT2!
« Reply #36 on: November 07, 2015, 12:44 PM »
hey I'm getting that error:
[attachment=1]
Same, just been ignoring it though because I can still host.  You having any problems hosting?

Snoopers mostly come with "build-in" WormsNAT2. So your local WKs aren't needed, when hosting via snooper.
<dream>
One day CyberShadow will push worms source code to github by accident…
</dream>

Offline Tomi

Re: Update your WormNAT2!
« Reply #37 on: November 07, 2015, 01:41 PM »
hey I'm getting that error:
[attachment=1]
Same, just been ignoring it though because I can still host.  You having any problems hosting?

Snoopers mostly come with "build-in" WormsNAT2. So your local WKs aren't needed, when hosting via snooper.
Yes, Great Snooper doesn't use any WormKit dll.. it has it's own Hoster.exe, which has the same code as Wormnat.dll, but in other programming language, and it is extended to make Great Snooper able to close the game on WormNet when it is started.

Offline bath

Re: Update your WormNAT2!
« Reply #38 on: November 07, 2015, 08:01 PM »
hey I'm getting that error:

# for hex 0x7e / decimal 126 :
  ERROR_MOD_NOT_FOUND                                           winerror.h
# The specified module could not be found.

Means you're missing a specific DLL that the module depends on. Visual C++ runtime maybe.

Offline StepS

Re: Update your WormNAT2!
« Reply #39 on: November 08, 2015, 06:51 PM »
Means you're missing a specific DLL that the module depends on. Visual C++ runtime maybe.
It's likely wkPackets.dll which was required by older versions, but is now out of date and causes problems if present.
If you're using The Wheat Snooper to host, you must update to 2.9.3, else it will keep trying to downgrade the module and cause you issues, such as skipped packets. Also, older versions will stop working after January 1st, 2016.
« Last Edit: November 08, 2015, 06:55 PM by StepS »
Dec 30 2013 23:59:44 <StepS> windowed mode isn't the only thing you need about frontend
Dec 30 2013 23:59:49 <StepS> you need it to be actually bigger
Dec 31 2013 00:00:13 <StepS> it actually is very small on my 15-inch full HD screen
Dec 31 2013 00:00:25 <StepS> while running at 640x480 or stretched mode makes it fuzzy
Dec 31 2013 00:00:44 <StepS> this problem has been around since the Worms Armageddon's release and no one has even tried to beat it
[...]