Yeah, it’s really not that obvious anywhere but it’s different to Bukkit, so it catches a lot of people out. That’s why I have base at the end of my permission nodes for commands. Otherwise, the basic node would be unusable for more advanced permissions, which would not have been ideal…
Hey @dualspiral am attempting to do something unique with the nucleus jail system. But in order to do it I need 2 separate jail settings. I one jail Id like people to have access to more commands than in another jail region. Would this be possible? I would like to use the secondary jail for a particular event, so I wanted to know if there was a way to do this or not.
Thanks
Riddle
No, there is not a way to do it, and I won’t be adding that either, because what you’re looking for is far more suited to some type of region protection plugin. I suspect FoxGuard might be able to do it, possibly with a custom handler, though I don’t know too much about it. Sorry!
Is this stable enough to make the change from essentials to this? Or should I wait a bit? I am on 1.10.2
I plan to release the next update on Saturday or Sunday, after I get a couple of extra features in, maybe wait until then so you just have to update once. I am aware that a couple of recent updates to Sponge might have caused an incompatibility with the latest 1.10.2 version, they should be resolved in the new build once it’s out.
Otherwise, yes, I believe so.
Alright much appreciated. Once you do this please let me know. Thanks 
I am using 1.8, Sponge 4.x
Unable to find any setting (or blind to it) that can suppress this debug noise:
23:30:47] [Server thread/INFO] [nucleus]: ItzMel0n ran the command: /sethome
[23:30:47] [Server thread/DEBUG] [nucleus]: Running io.github.nucleuspowered.nucleus.modules.home.commands.SetHomeCommand in async mode.
[23:30:50] [Server thread/INFO] [nucleus]: ItzMel0n ran the command: /sethome 1
[23:30:50] [Server thread/DEBUG] [nucleus]: Running io.github.nucleuspowered.nucleus.modules.home.commands.SetHomeCommand in async mode.
[23:30:52] [Server thread/INFO] [nucleus]: noobslayer09 ran the command: /delhome home
[23:30:52] [Server thread/DEBUG] [nucleus]: Running io.github.nucleuspowered.nucleus.modules.home.commands.DeleteHomeCommand in async mode.
[23:30:55] [Server thread/INFO] [nucleus]: noobslayer09 ran the command: /sethome shore
[23:30:55] [Server thread/DEBUG] [nucleus]: Running io.github.nucleuspowered.nucleus.modules.home.commands.SetHomeCommand in async mode.
[23:30:55] [Server thread/INFO] [nucleus]: ItzMel0n ran the command: /sethome a
[23:30:55] [Server thread/DEBUG] [nucleus]: Running io.github.nucleuspowered.nucleus.modules.home.commands.SetHomeCommand in async mode.
[23:31:01] [Server thread/INFO] [nucleus]: ItzMel0n ran the command: /sethome a1
[23:31:01] [Server thread/DEBUG] [nucleus]: Running io.github.nucleuspowered.nucleus.modules.home.commands.SetHomeCommand in async mode.
[23:31:04] [Server thread/INFO] [nucleus]: ItzMel0n ran the command: /sethome a2
[23:31:04] [Server thread/DEBUG] [nucleus]: Running io.github.nucleuspowered.nucleus.modules.home.commands.SetHomeCommand in async mode.
[23:31:06] [Server thread/INFO] [nucleus]: ItzMel0n ran the command: /sethome a3
[23:31:06] [Server thread/DEBUG] [nucleus]: Running io.github.nucleuspowered.nucleus.modules.home.commands.SetHomeCommand in async mode.
[23:31:15] [Server thread/INFO] [MinecraftServer]: [Playtester] ~zombie147: ight
[23:31:21] [Server thread/INFO] [nucleus]: ItzMel0n ran the command: /delhome a1
[23:31:21] [Server thread/DEBUG] [nucleus]: Running io.github.nucleuspowered.nucleus.modules.home.commands.DeleteHomeCommand in async mode.
[23:31:26] [Server thread/INFO] [nucleus]: ItzMel0n ran the command: /delhome a2
[23:31:26] [Server thread/DEBUG] [nucleus]: Running io.github.nucleuspowered.nucleus.modules.home.commands.DeleteHomeCommand in async mode.
[23:31:28] [Server thread/INFO] [MinecraftServer]: [Playtester][Admin] BooMod: now…
[23:31:32] [Server thread/INFO] [nucleus]: ItzMel0n ran the command: /delhome home
[23:31:32] [Server thread/DEBUG] [nucleus]: Running io.github.nucleuspowered.nucleus.modules.home.commands.DeleteHomeCommand in async mode.
[23:31:39] [Server thread/INFO] [nucleus]: TalFuller ran the command: /del home
[23:31:42] [Server thread/INFO] [nucleus]: TalFuller ran the command: /delhome home
[23:31:42] [Server thread/DEBUG] [nucleus]: Running io.github.nucleuspowered.nucleus.modules.home.commands.DeleteHomeCommand in async mode.
[23:31:46] [Server thread/INFO] [nucleus]: TalFuller ran the command: /sethome 1
[23:31:46] [Server thread/DEBUG] [nucleus]: Running io.github.nucleuspowered.nucleus.modules.home.commands.SetHomeCommand in async mode.
So is there any fix for the tick loop of the afk kick?
You can do this in GriefPrevention using the /cp commands which isolate permissions to a specific claim.
@blood would there be anyway to force the player to leave after a speicified time period? That was the reason I was looking at the jailing system. I know I can block the commands in GP. But its the forcing the player out of the area after a specified time that’s troubling me.
@Riddle While I don’t support the use of Jails for other than jailing and so would not make any “fixes” you would need if this doesn’t work, you could combine the two plugins, and as a result, what you could do is:
- Set up two (or more) jail areas that are also GP claims
- Whitelist every command that you would need in the “jail” cells in
main.conf. - Use permission isolation provided by GP to effectively decrease this whitelist for each claim/jail.
- Jail with the time period as normal.
Not sure if this is linked to you guys, or if it might be a sponge bug, but here you go:
Ok so this is a Sponge issue, but I talked to Blood and he said that if you just load the chunks before the player teleports then it will fix the issue.
Little bit awkward, but sure. I need to make some changes to the general Teleportation architecture of Nucleus anyway, so I can slip it in there. I’ll do it once I get a chance to, may not be for a few days due to something that’s cropped up on my end, I’m sorry to say.
A few days would be amazing, this is an issue my players have been dealing with for a while and I just recently found out what was causing it (Sponge), and I am sorry this is something you have to deal with. I really thank you for your hard work on this plugin!
Is it possible to disable the
<< >> in the motd?
Even without the title, these still are shown… I think it’s out of place and tacky.
@IBG_Nova Yeah, it’s something I’ll get done ASAP.
@Luke It’s part of the Sponge pagination service I use, but I have been looking at seeing if I can work around it, may ask the Sponge guys to expose the number of pages it’s broken it up into (if it can be obtained for that particular chunk of text) and if it’s only one, just send the text outside of the service. Either that, or see if we can add an option to Sponge to remove the back/next indicators.
Thanks! Sorry to be so nitpicky, just one of those things.
@dualspiral and or @HassanS6000 would you guys be able to integrate the book that players default got when they first logged in with the old kits plugin into the new one? I ask because I don’t know how else to make sure an item is in a new players inventory defaultedly without running an exterior command. I’m making a guide for all of everything on the server and I want to have all new players start with it in their inventory so no one has to tell them to do something like “Oh, run /kit Guide” or something, just want them to have it so they’ll see it first thing into the server.