Not really anymore info I can give other than that.
I am on the latest Sponge Forge and the Latest forge.
And we are running Pixelmon 4.2.7
Not really anymore info I can give other than that.
I am on the latest Sponge Forge and the Latest forge.
And we are running Pixelmon 4.2.7
This occurs in the stack trace: br.net.fabiozumbi12.redprotect.listeners.RPGlobalListener.onFireSpread(...)
. You should contact the developer of that plugin.
Thank you, I have contacted the plugin dev.
Hello,
This is the way i deny fire to spread on world:
Its the way i found… you can try allow firespread on your worlds (not in claims) or if other dev find other way to deny firespread. I tryed a lot of way and i find this only method.
An user says in the 1.10.2 RedProtect runs without lag compared with 1.8.9. I dont know what improvements 1.10 have but i really recommend.