I'm going to be restructuring the database used to store /pvp locations. Doing this while the /pvp command is disabled just makes it much simpler for me.
As such the /pvp command will be disabled for about 10 minutes early morning (server time, GMT+1.) If you get an 'unknown command' error while using /pvp -- don't be alarmed, it's only temporary.
All your locations will of course be saved, I'm not clearing the database.
I'll post when I disable it, and again when it's back up.
/pvp to be temporarily disabled
Re: /pvp to be temporarily disabled
Disabling it now
Re: /pvp to be temporarily disabled
Re-enabled it.
Edit: Re-enabled exactly 10 minutes after I disabled it, lol
Edit: Re-enabled exactly 10 minutes after I disabled it, lol
Re: /pvp to be temporarily disabled
Disabling it again. Getting a weird error. Trying to replicate it to find out what's going on, /pvp will be disabled until then. I'll be in console if somebody needs a manual teleport.
Re: /pvp to be temporarily disabled
Re-enabled again.
I had copied the code for the sql update query from the overworld -> pvpworld method. Turns out that for that query instead of getting the players current location, it just always saved 'world' (since it was the overworld -> pvpworld method, I figured only people in the aboveworld could use it hence why not retrieving the players current location was okay) But then when I copied the query over to the pvpworld -> overworld method today as part of rewriting the code, I forgot I'd done that. So if you were in the pvpworld and you used /pvp, it would always incorrectly save 'world' as your location. Causing all the problems. Fixed and tested everything is working fine now.
Pretty sure I caught this fast enough for only one person to have been affected, and I've manually helped him back. But in case anybody else was affected, please post saying so.
I had copied the code for the sql update query from the overworld -> pvpworld method. Turns out that for that query instead of getting the players current location, it just always saved 'world' (since it was the overworld -> pvpworld method, I figured only people in the aboveworld could use it hence why not retrieving the players current location was okay) But then when I copied the query over to the pvpworld -> overworld method today as part of rewriting the code, I forgot I'd done that. So if you were in the pvpworld and you used /pvp, it would always incorrectly save 'world' as your location. Causing all the problems. Fixed and tested everything is working fine now.
Pretty sure I caught this fast enough for only one person to have been affected, and I've manually helped him back. But in case anybody else was affected, please post saying so.
-
RevStoningpot
- Moron
- Posts: 2477
- Joined: Sat Aug 13, 2011 12:39 pm
- Location: first star to the right and straight on till morning
- Contact:
Re: /pvp to be temporarily disabled
It made me lose 100 diamonds and my full portection IV diamond aromor
-
waronchickens97
- in diamond armor
- Posts: 445
- Joined: Sun Jan 08, 2012 6:27 pm
- Location: The other side of a mobious strip.......
Re: /pvp to be temporarily disabled
I lost 64 stacked sets of prot 4 diamond and 12 stacks of d blox, apong with some sharp X fire V's and prot 10 unb 10. Oh and a stack or two of ghast tears and same of blazerods, and 9 stacks of 64 water bottles. Not to mention my 20 story endergrinder.
-
LoneSoldier55
- Moron
- Posts: 4391
- Joined: Thu Jan 05, 2012 6:40 pm
- Location: Equestria, Visiting Billy Mays
Re: /pvp to be temporarily disabled
The joke was already made, quit beating it to death.waronchickens97 wrote:I lost 64 stacked sets of prot 4 diamond and 12 stacks of d blox, apong with some sharp X fire V's and prot 10 unb 10. Oh and a stack or two of ghast tears and same of blazerods, and 9 stacks of 64 water bottles. Not to mention my 20 story endergrinder.