Jordan
Jordan
Yeah you should never be using one database for multiple servers for P2...... This is not an "oversight"... It does not make SQL useless? It was never designed for multiple...
> I think you are misunderstanding what I meant. Yes Bungeecord is not the reason why it is no working. But yet, it is - or more the generell idea...
We need the full log. The SQL manager in P2 does play around with autocommit, and it could be caused by a race condition, or an error somewhere causing autocommit...
> I can send you a log via DM. I'd have to prepare it for you, as there are almost 200 players per server online at any one time, so...
For instabreak P2 uses Block#breakNaturally and I do not know what event(s) that would send, and what it would be determined as have being "done" by
I do not believe this data is stored in the schematic - would be "fixed" by #2746
Are you able to try and identify when that started in the log?
Did you have a regenallroads scheduled..? I don't know how or why this queue would suddenly appear
You're not using FAWE there though, that's a normal Minecraft command?
Okay, so where and how is FAWE actually being used...? You've shown us a `/fill` command which is not FAWE - it is a default Minecraft command