So if people were to find another way to hack Srb2, you guys would update again?
So if people were to find another way to hack Srb2, you guys would update again?
So if people were to find another way to hack Srb2, you guys would update again?
There are so many things wrong with your assumption that it's hard to even begin, etc.
Oh great a huge update for netgaming
There are so many things wrong with your assumption that it's hard to even begin.
If a player edited SRB2's source code to change the player's abilities, and then they tried to play a game online, they'd get kicked for consistency failure. The server and client are constantly passing information back and forth to each other, and when the client tells the server information that conflicts with what the server sees, the server will try to fix it, and if it can't, kick the offending player. This is not to say that there aren't ways to edit the game's code in an attempt to cheat, but you can't edit the game rules themselves, because the server is checking for that.
There is the problem that it was a mistake to release the source code, so I see so many hackers.
Whether or not it is a mistake, STJR had to release the source code regardless, because SRB2's code falls under the GPLv2 license.
[...] but there must be some methods to stop these hackers [...]
The filesize can vary pretty wildly based on how you compile it, and whether the win or sdl version is used. I don't really know any specifics, other than that the inclusion of some debugging settings can shoot the size up quite a bit.My biggest question is, how the heck did you knock 840Kb off the file size?
As Mystic stated above, the bug that allowed hackers to mess with other people's games has been fixed. No need to fret now.
EDIT: Just downloaded the patch.
![]()
My biggest question is, how the heck did you knock 840Kb off the file size?
This may not be a 2.1 release, but it's the next greatest thing. I was blaming WINE hitherto for SRB2 not generating screen captures accurately, but it appears that this was veritably caused by the diminished framerate in SRB2 itself as a consequence of executing non-native binaries. I'm glad too that the laser issues were resolved. There should (hopefully) be less consistency failures during the CEZ levels and some of the netplay levels with laser FOFs with this 2.0.7 revision.