- Wed Oct 26, 2011 8:07 am
#41110
First, a few starting notes...
1. That's "flight," not "fight." This is my first post, not an edit, but the "l" could easily be missed.
2. I saw a couple topics on help bot suggestions, but I consider this problem to be big enough for it's own topic, due to the number of related banning cases.
3. I only looked at the first 2 pages, so if there is a similar topic, please tell me.
On to the main subject. For those of you who may be unaware, the help bot has a glitch that can sometimes ban a player for "flying" when they are not. This usually occurs when a player is lagging, in conjunction with one of the following situations:
1. The player has just tp'd (teleported). This includes using things like the /trade command.
2. The player was in an area where they can't build, and placed a block under themselves while jumping (sometimes to reach an area they shouldn't be in
).
3. The player was in an area where they CAN build, and placed / destroyed blocks they were standing on. (This one requires lagging, and is the one that happened to me. My [UNBANNED] Appleal is here: http://minerealm.com/community/viewtopi ... 108#p41108)
My most likely theory as to how this is happening is that the client (the player's minecraft program) has not received packets that it should have containing terrain updates, and so has moved the player somewhere they should not be able to go (or NOT moved the player somewhere they should have gone). The packet containing the players new location successfully reaches the server, and help bot notices that the player is somewhere that they shouldn't be.
EX: I placed a workbench and then destroyed it, but due to connection issues, the workbench "reappeared" (the server hadn't yet been informed that I destroyed it), so I jumped up on top of it and my client started sending my new position (on top of the workbench). Next, the server recieved information that I had destroyed the workbench, so it is removed server-side, but the packet confirming it's destruction fails to reach my client. My client, however, successfully sends it's next (few?) packets saying I'm standing on top of the workbench (which no longer exists server-side), and so to the server, it looks like I'm standing one block above ground without falling (and thus flying), leading help bot to ban me.
I apologize for the large explanation, but I believe it to very likely be how this is working within the program(s), and didn't want to keep back any details that could be important.
So, as for possible solutions, IF this is the nature of the glitch...well, I'm having a hard time with that, unfortunately... The only things I've thought of so far are not actual solutions to the glitch, but may be helpful, nonetheless:
1. When help bot detects flying, make it tp the player to the last "legit" location, and kick them with a warning (not ban them). If this works correctly, a player who is ACTUALLY flying should get kicked IMMEDIATELY when they start trying to fly, and when they log back in, they should be where they were just before trying to fly.
2. If the above doesn't work, a repeated offense banning might be helpful (if not nearly as effective). First time is a warning, second is a warning + kick, third time is banning. Unfortunately, since I ran into this glitch my first day on the server, it's likely that some players with bad connections will still reach the banning offense without actually flying. Also, depending on the implementation, it may also be possible for a player who IS flying to exploit this more relaxed behavior to reach somewhere they shouldn't be.
*Exhales*
Looking forward to other peoples' thoughts / other solution ideas, as well as a possible fix from Intelli and / or other admins in the future.
1. That's "flight," not "fight." This is my first post, not an edit, but the "l" could easily be missed.
2. I saw a couple topics on help bot suggestions, but I consider this problem to be big enough for it's own topic, due to the number of related banning cases.
3. I only looked at the first 2 pages, so if there is a similar topic, please tell me.
On to the main subject. For those of you who may be unaware, the help bot has a glitch that can sometimes ban a player for "flying" when they are not. This usually occurs when a player is lagging, in conjunction with one of the following situations:
1. The player has just tp'd (teleported). This includes using things like the /trade command.
2. The player was in an area where they can't build, and placed a block under themselves while jumping (sometimes to reach an area they shouldn't be in
).3. The player was in an area where they CAN build, and placed / destroyed blocks they were standing on. (This one requires lagging, and is the one that happened to me. My [UNBANNED] Appleal is here: http://minerealm.com/community/viewtopi ... 108#p41108)
My most likely theory as to how this is happening is that the client (the player's minecraft program) has not received packets that it should have containing terrain updates, and so has moved the player somewhere they should not be able to go (or NOT moved the player somewhere they should have gone). The packet containing the players new location successfully reaches the server, and help bot notices that the player is somewhere that they shouldn't be.
EX: I placed a workbench and then destroyed it, but due to connection issues, the workbench "reappeared" (the server hadn't yet been informed that I destroyed it), so I jumped up on top of it and my client started sending my new position (on top of the workbench). Next, the server recieved information that I had destroyed the workbench, so it is removed server-side, but the packet confirming it's destruction fails to reach my client. My client, however, successfully sends it's next (few?) packets saying I'm standing on top of the workbench (which no longer exists server-side), and so to the server, it looks like I'm standing one block above ground without falling (and thus flying), leading help bot to ban me.
I apologize for the large explanation, but I believe it to very likely be how this is working within the program(s), and didn't want to keep back any details that could be important.
So, as for possible solutions, IF this is the nature of the glitch...well, I'm having a hard time with that, unfortunately... The only things I've thought of so far are not actual solutions to the glitch, but may be helpful, nonetheless:
1. When help bot detects flying, make it tp the player to the last "legit" location, and kick them with a warning (not ban them). If this works correctly, a player who is ACTUALLY flying should get kicked IMMEDIATELY when they start trying to fly, and when they log back in, they should be where they were just before trying to fly.
2. If the above doesn't work, a repeated offense banning might be helpful (if not nearly as effective). First time is a warning, second is a warning + kick, third time is banning. Unfortunately, since I ran into this glitch my first day on the server, it's likely that some players with bad connections will still reach the banning offense without actually flying. Also, depending on the implementation, it may also be possible for a player who IS flying to exploit this more relaxed behavior to reach somewhere they shouldn't be.
*Exhales*
Looking forward to other peoples' thoughts / other solution ideas, as well as a possible fix from Intelli and / or other admins in the future.
~Laike_Endaril~
