NOTICE: Due to a rise in bot activity, new posters need to be approved before posting.Join the community Discord server!
Well screw me over, I used the search to look up "2 Sentries" "Double Sentries" "Two Sentries" and even "Double Autogun"But not "Siamese Autogun" :c
Quote from: MR MAGN3TIC I don't like it. Oh, well, you might as well pack up and stop now, because he doesn't like it
I don't like it.
http://www.ganggarrison.com/forums/index.php?topic=10939.0Hum, medo said this would be fixed. :I
I found the bug, it happens because of desync (as so many other things do.) The following description is for later dev reference so don't worry if it's unclear .The client thinks that the autogun is ready and creates the Turret object, but on the server the enemy shot registered before the autogun was actually done and it's deconstructing. With the next QUICK_UPDATE the client is notified that the autogun is not complete, but the turret is not destroyed, so we see both the turret and the deconstruction animation.When that happens, the autogun won't actually deal damage until it finished constructing on the server, even though it appears to be firing on the client.I won't fix this for 2.1.2 though, because it requires changes to the networking, and I want 2.1.2 to be compatible with 2.1.1.
Quote from: MedO on September 14, 2009, 03:59:47 pmI found the bug, it happens because of desync (as so many other things do.) The following description is for later dev reference so don't worry if it's unclear .The client thinks that the autogun is ready and creates the Turret object, but on the server the enemy shot registered before the autogun was actually done and it's deconstructing. With the next QUICK_UPDATE the client is notified that the autogun is not complete, but the turret is not destroyed, so we see both the turret and the deconstruction animation.When that happens, the autogun won't actually deal damage until it finished constructing on the server, even though it appears to be firing on the client.I won't fix this for 2.1.2 though, because it requires changes to the networking, and I want 2.1.2 to be compatible with 2.1.1.wat
Sorry for the strange topic name. It seemed like a proper name to call the phenomenon at the time.
Maybe we should be able to "tag" bug report threads.
It is the business of the future to be dangerous; and it is among the merits of science that it equips the future for its duties.
[...] if you have a large enough codebase, any class of error that is syntactically legal probably exists there.