Is there any advantage of this? The old way was working well too. Am i right that now anyone have to have that dll to use wnat?Not sure what you mean, but nothing changed in how you have to use WormNAT2.
Is there any advantage of this? The old way was working well too. Am i right that now anyone have to have that dll to use wnat?
Hello
Files changed the same error
(http://images70.fotosik.pl/1195/e95b97010e31c517med.jpg) (http://www.fotosik.pl/zdjecie/e95b97010e31c517)
Since I upgraded, WormKit started to acting weird. Icon is not even there anymore, like it got erased.
Even snooper sending me some error messages before hosting the game.Unfortunately I can't do anything about this.
Btw, 2/3 games I hosted disconected after aproximately 10 minutes. I'm hosting every night, and never had problems until today.Can you post some replays?
Basically, this update screwed me up somehow. Is it possible to downgrade on older version?You can get the older version from here (http://worms.thecybershadow.net/wormkit/wkWormNAT2-2015-07-27.zip), but again, this version will stop working in January. It would be better to fix whatever problems you have with the new one.
Ty.
Can you post some replays?Here they are:
About worms version and built-in wormkit support - don't know man..it's like you talking to the wall atm :) Gonna try fix this, if I found solution, others experiencing similar problem (if there are any) will be informed.
EDIT: using 3.7.2.1. if that was your question.
Unless you use any modules that MUST be loaded before the game starts, you can just delete your WormKit.exe and instead enable "Load WormKit modules" in the game's advanced options.
I never really. I could even host with my dormitory net using some japanese free vpn. And I didn't get wrong feedbacks about the wormnat2 implementation in great snooper.Is there any advantage of this? The old way was working well too. Am i right that now anyone have to have that dll to use wnat?
never experienced skipped packet desynchs? will be glad if this will be erased now.
The way snooper authors added WormNAT2 support was to modify the module's code and use my WormNAT2 server without my permission. I have not been happy about this, but I've let it slide because ultimately it's a net benefit to the community. However, what you are seeing is the consequence of their choices - I can't update things on my side without possibly breaking things for unofficial WormNAT2 clients. The snooper API is not something I came up with, I adapted something that was already out there, and even though it worked in our tests, it takes two parties to create a stable and working API.Oh man.. I wish I would still have the logs of our long-long conversations we had, but I guess you can't even remember me. I remember that I asked for your permissions under the whole development of my snooper. Only one man have done what you said here. Don't get me wrong here, this just feels bad a little coz I am that type of man.
About snoopper error msg - it's not actually error, but some kind of a warning. Like: "you hosted too many games recently" (still able to host, but that msg is just annoying). I guess snooper creators would do something about that in next upgrades. We'll be patient until then.Sorry that's my fault of lazyness. That can be that error as the error message says, but it can be communication fail too.
Unless you use any modules that MUST be loaded before the game starts, you can just delete your WormKit.exe and instead enable "Load WormKit modules" in the game's advanced options.
Actually I had WormKit and W:A icon before. After upgrading - WormKit.exe just deleted on its own. On the other hand,moduls working like they supposed to. So basically, only weird thing are that disconnections we experienced tonight. Like i said, highly doubt it was modem problem.
Hm.. just experienced one more. Can't open replays at all anymore. Trying to put W:A to open .wagame files but nothing happens.
The new zip file just contains two DLLs, installing which would definitely not affect things like your WormKit icon and whether you can open replays. You have something else going on.
But agree with Kaleu there, I also downgraded wormnat2 last night. Seems more stable, at least for my pc.
So, can this Wormnat host games by snooper without creating packets file?Yes in theory, but it depends on your snooper as well. Ask your snooper author.
But agree with Kaleu there, I also downgraded wormnat2 last night. Seems more stable, at least for my pc.
Please, we need to test the new version, find bugs and fix them (assuming there are any!). If we are afraid of moving away from old versions, we will never make progress. This is especially important because many people do not post on TUS and will never see this thread, and I will never find out or be able to debug and fix any problems they will run into. The old versions will stop working in January, which is a fair way off, but it's best if we fix all problems as soon as possible.
I've had no problems at all with the new version. Thanks CyberShadow for the update.
hey I'm getting that error:
[attachment=1]
hey I'm getting that error:Same, just been ignoring it though because I can still host. You having any problems hosting?
[attachment=1]
hey I'm getting that error:Same, just been ignoring it though because I can still host. You having any problems hosting?
[attachment=1]
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.hey I'm getting that error:Same, just been ignoring it though because I can still host. You having any problems hosting?
[attachment=1]
Snoopers mostly come with "build-in" WormsNAT2. So your local WKs aren't needed, when hosting via snooper.
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.It's likely wkPackets.dll which was required by older versions, but is now out of date and causes problems if present.