2 of my player have come to me with an issue, the issue seems to be that all the ps they own are missing, just gone, don't exist anymore, one of the player have had this issue before, replaced them and now they are gone again, the other just noticed that his fields are gone, I have tried to replicate this issue myself but cant figure out why they just deleated themselves. is there a command or something that a player can run that will remove ALL the ps fields?

Something similar has been happening on my server as well with v10.1.0. Player's fields almost invariably always end up disappearing. The block remains but it does not register as a field any longer. I'm wondering if it has something to do with SQL changes that maybe you fixed 9 days ago? (I THINK my version came from before that time... built it myself).

Gonna have to roll back all those code style updates.

It looks like v10.1.0 was before that change. Looks like you bumped the version to 10.1.1 with those recent changes. Also, not seeing any errors or anything. I've tried a few things to come up with reproduction steps but no luck.

I'm not with the server anymore, but what I could see is that the players effected were staff on my server, they had ps bypass on and placed more then what they were allowed to, so when they turned ps bypass off, the old ps fields they had would orphan them selvs, and when the turned ps bypass back on, the newer ps fields would remove as well, this has ONLY happened to the staff on my server, only because they had the ps bypass. that was the only way I could replicate the issue. like I said, I'm not with that server anymore because the co owner thought it would be nice to take full control after I fixed everything for him, so I am available to help anyone in need, if they cant figure something out

Ah, in my case this is happening to everyone, regardless of bypass
permissions.

On Tue, Mar 15, 2016, 01:02 dwa1275 [email protected] wrote:

I'm not with the server anymore, but what I could see is that the players
effected were staff on my server, they had ps bypass on and placed more
then what they were allowed to, so when they turned ps bypass off, the old
ps fields they had would orphan them selvs, and when the turned ps bypass
back on, the newer ps fields would remove as well, this has ONLY happened
to the staff on my server, only because they had the ps bypass. that was
the only way I could replicate the issue. like I said, I'm not with that
server anymore because the co owner thought it would be nice to take full
control after I fixed everything for him, so I am available to help anyone
in need, if they cant figure something out

—
You are receiving this because you commented. Reply to this email directly
or view it on GitHub:
#922 (comment)

do you get any sq errors in your log, and if so, can you post them

as well as pm me your server, ill come and play with them a little, as a player, nothing more, I know some are tight with there server groups and such

Actually, I noticed when I broke the block and replaced it with a new field
block that there was some error about a unique key. That is now buried in
my logs but I can try to reproduce it tomorrow.

On Tue, Mar 15, 2016, 01:05 dwa1275 [email protected] wrote:

do you get any sq errors in your log, and if so, can you post them

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:

#922 (comment)

if you break it in creative, you orphan the ps, with means the field is still there, but when the cleanup does its thing, it will be removed. you can do /ps clean to remove all orphaned fields if you think you have many and just make sure your staff doesent remove in creative, as well as if you are trying to just remove some ones ps, use /ps take

Hmm, I could swear creative previously removed them just fine. In the case
I mentioned this was a field that was no longer working (/ps info and /ps
visualize say no field).

On Tue, Mar 15, 2016, 01:11 dwa1275 [email protected] wrote:

if you break it in creative, you orphan the ps, with means the field is
still there, but when the cleanup does its thing, it will be removed. you
can do /ps clean to remove all orphaned fields if you think you have many
and just make sure your staff doesent remove in creative, as well as if you
are trying to just remove some ones ps, use /ps take

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:

#922 (comment)