Thread title: Sg player bug Minecraft Username: skymaster200 Brief Description: beddie22 was playing in an sg [sg2] with me and other and when i tried to kill him he had the dieing animation and i got his exp. He came running at me again and he got slained out. this refers to him some how respawning Instructions: im not sure how this was done, because the bug didnt happen to me. List the steps needed to take to reproduce this bug. Add more or less instructions appropriate to getting to the bug. If it's just a single step or ten steps, just add the numbers accordingly. Numeral listing is preferred. How many times did you recreate this bug?: im not the person the bug happened to. beddie22 is the one who had the bug happen to them Result: you get stuck in an sg and lose your exp Expected Result: you get stuck in an sg and lose your exp Evidence: i didnt get any screens of this
Ah, now I begin to understand this bug...couldn't for a while. If I understood it right the game usually kicks you before you die if your health is 0. This seems like the kick didn't happen and thus he respawned in the world he was in. at least that's what I think, would make sense.
If this occurs, it is best to inform that person to do "/sg join". That will let him leave the game and take him back to the SG board. If I'm correct, this was reported before, and was known to be fixed.
Thanks jamie I will look into it, The new worldguard update was a major overhaul as I have said before and we are still tweaking things.
Mhm...it really looks like a major overhaul. So many things changed. Is the "Hey!" message the new default one, or can they be customized now? And I still have no idea what the "*" after the names on /rg i mean. The grey text below doens't really help. :/
Yes that message can now be customized and as for the '*' after the names in /rg i, its the users last seen name. It is for support users being able to change their names. It displays their name in /rg i but its actually bound to their UUID now.
Aaah, that cleared a lot of my questions. Isn't it interesting how the fix of a bug usually causes at least one new bug?
Awesome. Mhm, I know how easy that happens...my currently biggest program (2000 lines in Delphi) once had 3 bugs in Version 1.0.0...now it has 11 fixed and 7 unfixed ones in version 1.2.4. Anyway, back to the original topic...this bug seems to love surviving any SG patches, right?
This is actually a wg bug. Might be able to patch it if I have access to the sg repo, which andrew still has to transfer to phys.
