-shrugs- Probably.
Have an ETA on that rewrite you mentioned in the IRC?
I couldn’t reproduce it, but it found me itself. I again caught the bug which was described a few posts above. But now I have the log. The server crashed at startup. The consequences are the same as in the previous my posts. Who is to blame? Forge? SpongeForge? FoxGuard?
latest.log
fml-server-latest.log
crash-2016-09-13_00.30.32-server.txt
forge-1.10.2-12.18.1.2079-universal.jar
spongeforge-1.10.2-2079-5.0.0-BETA-1719.jar
FoxCore-0.9.3-api5-146-server.jar
FoxGuard-0.19.2-dev-api5-298.jar
Your server logs do not match your crash log.
Are you sure you sent me the ENTIRE server log?
Regardless… Go to your server properties. What is your max-tick-time set to?
Actually it just appears that FoxGuard was unable to create/open a file.
This seems to be an OS specific issue, and you’re the only person i’ve seen have it.
It works fine for other people. There’s nothing i can do about this. Sorry.
Is there a way to set it so new joiners automatically go into the members group?
unfortunately no.
So, if i create a region everyone can break it until i physically add them to members?
Er usually you do the exact opposite. no one can break it until added to members.
That’s what the default group is for.
Everyone is in the default group, no matter what.
Full logs:
latest.log
fml-server-latest.log (part 1)
fml-server-latest.log (part 2)
crash-2016-09-13_00.30.32-server.txt
max-tick-time=60000
This suggests that the impaired file, which stores links.
Windows 7 Pro x64 Rus + full updates
Java 8u102 (build 1.8.0_102-b14)
sadly
Yeah, when FoxGuard tried to open a database file it just hung. It probably has to do with your OS.
I highly recommend running FoxGuard on Linux instead of Windows.
While that doesn’t mean that FoxGuard doesn’t support Windows, it just means that Windows is known to have a lot of problems involving file access that Linux does not.
So does it auto set that you cant break blocks in the default group or do you have to do a command?
you have to set it to be that way with a command.
/fg modify handler handlername flags default block break =false
I’ve made a new release of FoxGuard, available for both API 4.2 and 5.
You can find it here:
FoxGuard version 0.19.3-dev for SpongeAPI 4.2 and 5
Also don’t forget to grab FoxCore as well:
FoxCore version 0.9.4 for SpongeAPI 4.2 and 5
Enjoi.
I don’t know if I missed anything, but I was bouncing my head off of my desk about a week ago trying to figure out how I was misusing the tristate parameters to set a flag, and I ended up giving up, and installing a different world protect plugin (The blasphemy, I know) and it wasn’t until just now I saw this comment and I want to know; Is this change documented somewhere? I wasn’t able to find AT ALL what I was doing wrong until this. So… maybe a quick change to the wiki?
This is mentioned, in passing, in the wiki on the Flags page.
I actually decided a few hours ago to do a quick re-write of things to make it clearer. Just got back from work so will begin that now. If you have other queries let me know and I’ll help if I can.
If you look at https://github.com/FoxDenStudio/FoxGuard/wiki/Basic-Handler
You will see under the flags section, it gives you the command syntax in full, and specifically states to not forget the equals sign. I’ve clarified a little bit more now, but it’s been there. @Inscrutable was the one that wrote it I believe.
As for documentation of the flags themselves, look here: https://github.com/FoxDenStudio/FoxGuard/wiki/Flags
That should be most of the info you need.
GUYS GUYS I MADE A NEW VIDEO!!!11!!11!! LIKE OMG!!!
YOU’RE WELCOME!
…
I do go a lot faster in this video than in the previous one, so do keep in mind I skip quite a bit of explaining.
2 Likes
How many attempts did it end up being? 