Vn. I remember this thread:

http://beta.team17.com/showthread.php?t=30386

Thanks for the memories. 

Awesome work, Ryan!  I'm proud of you!

What's a "mem"?  Was "memes" meant instead?

I'm sorry, but although many of the comics are funny, the weak English skill degrades much of the humor for me.  It's very distracting.

I realize I don't really have a right to criticize.  I just wanted to add my voice to the general public opinion.  I do respect the effort that's been put into these, having made a comic myself in the past.

What happens if you disable "Use double buffering" in the advanced options menu?

To get to the advanced options menu, make sure you're running the latest version of WA (3.6.31.0), then from the 4-tile WA main menu, click the bottom-right button with question marks, then click "Advanced".

Doing this might introduce screen tearing while scrolling, but might also fix frame drops.  Please try this and tell me the results.  I am not sure exactly what your problem is, so I'm not sure if it'll work, but I think it's useful to try.

Harpy, your post doesn't make much sense in English, but it sounds like you're suggesting a feature that already exists.  When everyone's bulb is lit, the game announces the version of the engine which will be used.  At the time of this post, if everyone is using the latest version, the version number announced will be "3.6.31.0".  If anyone is using an earlier version, the game will announce what old version will be emulated and who has that version.

With some small exceptions (such as Silkworm), the cheats discussed in this thread are relevant to the latest version of WA, 3.6.31.0.  For now, the best thing we can do about cheating as a community is inform each other about what's possible and how to detect how and why it's happening so we can avoid or prevent it.

Regarding Silkworm, it can only be used with version 3.0 of WA.  If your game says it's emulating version 3.0, the person with 3.0 is either using Silkworm or doesn't know about the updates.  It would be wise to refuse to play with them until they update their game.

- I know what these cheating does -
01. wkShopperDoubleSpace.dll = Doublespace used in TTRR
02. Silkworm = Doublespace with timing
03. UWT = Doublespace
04. xSpeed = Tool to speed up or speed down
05. Tool Assisted = You can controled every steps on worms
06. Autohotkey = Macro scripts

- But does anyone what these new cheating thing is? -
07. wkAutoKeys.dll = ?
08. wkCheatPack.dll = ?
09. wkKawooshKickNoMsg.dll = ?
10. wkLobbyCheating31.dll = ?

Here are many reasons I don't play TUS because of these cheating stuff. I bet here will be 75% cheaters on TUS. I hope CS would fix those stuff and disable it in next update, before I want start to play TUS again.

     

There's a lot of misinformation in this thread.

Firstly, Komodo, you should know by now that when a player injects an informative-only WormKit module which doesn't affect the underlying game state, there is no way for the opponent to know it's running, whether they ran WA via WormKit or not.  WormKit is only a means of loading WA.exe with any dll files named wk*.dll in the same directory.  It doesn't do anything beyond that.  Its source code is extremely small.

If someone is using a module which allows them to see the contents of crates dropped, there is no way for the opponent to know.  The only fix for this is to eliminate the logical loophole which enables the game to know the contents of crates.  I thought this loophole had been closed, but apparently a different loophole still exists to be exploited.  If anyone knows exactly what the loophole is, what the program does, or can send the program to CyberShadow or Deadcode to reverse-engineer, doing so would go a long way in helping them fix it.

Edit: I was just informed that this loophole allows people to see the other players' inventories, not crate contents.  I misunderstood.  It goes to show just how much misinformation and miscommunication we have surrounding these cheats.  If we work hard on communicating with each other well, we can better handle cheaters and put them to justice.

Secondly, the special tool-assist builds used to make those replays (such as the tool-assisted mission records here) generate encrypted replays which can not be played back by any public build of WA, and they can also not be used online since they have all their network code removed.  The replays on the WKB there have been personally decrypted by either Deadcode or CyberShadow specifically to be played back by public builds of WA, with the information that the replay is tool-assisted, so it belongs in its own category of competition, separate from unassisted replays.  It is not possible for anyone with a tool-assist build of WA to cheat in any competition without explicit permission and decryption by Deadcode or CyberShadow; something that will never happen.

Tool-assisted speed-running is not a form of cheating.  It is a separate competition between other players with tool-assistance and serves as a demonstration of the limits of the game's mechanics.  It's also meant as a form of entertainment.

As long as a replay is labelled as "tool-assisted", you can be sure that it was not played with the standard build of WA and can disregard it.  There will never be any tool-assisted replays which are not labelled as "tool-assisted".

If someone edits a replay, there will be many checksum mismatches, which you can see in the chat window during playback.  Editing a replay submitted to an unassisted competition is a form of cheating, and if you see checksum mismatches during playback, be aware that it was very likely to be edited.

Thirdly, there's the exploit to start the game without the light bulbs being lit.  We thought that loophole was closed, but there seems to be another way to do it.  CyberShadow and Deadcode both know about it, but don't necessarily know how it works exactly.  If anyone knows exactly what the loophole is, what the program does, or can send the program to CyberShadow or Deadcode to reverse-engineer, doing so would go a long way in helping them fix it.  Until it's fixed, I guess my only advice is to team in quickly and/or not play with people who use it.  It's pretty stupid anyway.  It doesn't really help anyone cheat; just makes the game start when people aren't ready, which can cause them to quit or have to rehost.

Fourthly, xSpeed (or other similar speed hacks) can be detected.  During online play, watch out for consistently-spaced periodic lag during most of the player's turn, as this is sometimes indicative of a speed hack.  If you suspect anyone of using a speed hack and you have their replay (can't be detected from your replay if you played with them online), send their replay to someone in #worms on the GameSurge IRC network or in a PM here to MonkeyIsland, KRD, CyberShadow, or me.  We have found cheaters using speed hacks before and we will continue to do so.  Everyone who isn't a cheater agrees that hardcore cheating like this is not okay.

Fifthly, KawooshKick simply disconnects people from the host and can only be used by the host.  It's not something that can be prevented.  If you get disconnected by the host seemingly without reason when you were doing well against someone who acts immature, you might be right to suspect foul play.  If you never want it to happen again, avoid playing with that player.  Also, tell other people that happened to you.  If it happens to multiple people, it can probably be decided that the person was cheating.  Anyone can do what KawooshKick does with a little bit of networking experience, without the module.

If you find cheat files, please send them to CyberShadow.  He is an excellent reverser and is able to determine what they do so he can fix their loopholes.  Both CyberShadow and Deadcode only want what's best for the WA community.  WormKit and wkMagic (which inspired wkRubberWorm and wkProjectX) were created to enhance the game with fun features, but unfortunately there are people out there who want to get an undeserved edge.  We can fight back if we communicate and work together.

Please include more detail.  Otherwise, nobody will be able to help you.  Posting the log itself is generally a good idea.  Also, sending it where the error message tells you to send it is a good idea.

More recent Edit than the Edit below: I have made some balance changes to the scheme.  Do not ignore this post, despite the contents of the below edit.  I have updated the Dabble scheme.  You can see the correct file history here: http://worms2d.info/File:Dabble_and_Fidget.wsc  Also, the link below is correct.

Edit: Good work, DumbBongChow.  This scheme is correct (at the time of this edit).  Man, I should really read all the comments before posting something like this.  

The correct version of the scheme is linked in the WKB article, and is not the one used in the example replay (which is a replay with an early, unfinished version of the scheme, submitted by Run at the time).

The correct scheme is here: http://worms2d.info/images/6/6c/Dabble_and_Fidget.wsc

If this is different from the scheme used for this tournament, please update the tournament's scheme.  I don't mind if you don't want to do that work, but it would help me contain this confusion about which scheme is correct.  Thanks so much for being interested in this scheme!  I love it, and I'm glad others do too.