I was making an info page, and I accidentally deleted the “Colors.txt” file, so I have no clue how to add a second page to a single info txt file. What is the notation for creating a second, third, etc page for an info card?
You don’t need to. Sponge paginates it automatically, so just write, and it will be paginated by itself.
1 Like
Could this feature be added? I am using the info section to create a step-by-step list, and I would like it all to fit on one page. If I start it at the bottom of the first page, it would be broken up. Not a huge deal I guess, but annoying and it does not look as professional overall.
No, because I don’t have control over how the Sponge pagination works and there is no clean way to do it. I can’t just add a number of linebreaks in, for servers that switch over to the Unicode character set, different handling would be required due to different character widths. If Sponge was to implement a “page break” in pagination, then I could work with it.
You might just have to add line breaks in yourself to solve it by trial and error or just create a new chapter in a separate text file.
+1
I also thought about it.
Sorry, me again.
I am having trouble setting up the chat colors to work for my groups. Everything is going directly to the default chat color. I have the latest Nucleus, latest PermissionManager, and the latest 1.10.2 Sponge. I already checked and I ensured that the rank names were the exact same (caps and all) and copied the formatting of the Default Template, yet everything just goes back to the default color. Here is a look at the chat sections of the config. Is my formatting wrong somewhere?
If I knew how to create a spoiler, I would.
EDIT: The code is in @KingGoesGaming post below this one, as he was kind enough to format it for me 
made your config more readable
chat {
# If "true", Nucleus will attempt to modify the chat
modify-chat=true
templates {
# The default chat template if no group templates apply.
default {
# The default colour for a player's chat if the "chatcolour" permission option isn't set on the player or group. Takes the same input as the "namecolour" option set to "" to retain default behaviour (no change of colour).
default-chatcolour="7"
# The default styles for a player's chat if the "chatstyle" permission option isn't set on the player or group. Takes the same input as the "chatstyle" option set to "" to retain default behaviour (no style).
default-chatstyle=""
# The default colour for a player's name if the "namecolour" permission option isn't set on the player or group. Takes the same input as the "chatcolour" option set to "" to retain default behaviour (no change of colour).
default-namecolour="f"
# Sets the prefix to a message. {{prefix}} - prefix (set as an option in a permission plugin), {{suffix}} - suffix (set as an option in a permission plugin), {{name}} - real name, {{displayname}} - display name
prefix="{{prefix}} {{displayname}}&f: "
# Sets the suffix to a message. {{prefix}} - prefix (set as an option in a permission plugin), {{suffix}} - suffix (set as an option in a permission plugin), {{name}} - real name, {{displayname}} - display name
suffix=" {{suffix}}"
}
# Group templates override the default chat template based on the users group. Note that the group name is case sensitive.
# Weight matters, the player will use the highest weighted template in this list that matches a group they are in, including inherited groups. If the same weight is used on two or more entries, the group with the most parents will be used.
group-templates {
Alpha {
# The default colour for a player's chat if the "chatcolour" permission option isn't set on the player or group. Takes the same input as the "namecolour" option set to "" to retain default behaviour (no change of colour).
default-chatcolour="a"
# The default styles for a player's chat if the "chatstyle" permission option isn't set on the player or group. Takes the same input as the "chatstyle" option set to "" to retain default behaviour (no style).
default-chatstyle=""
# The default colour for a player's name if the "namecolour" permission option isn't set on the player or group. Takes the same input as the "chatcolour" option set to "" to retain default behaviour (no change of colour).
default-namecolour=""
# Sets the prefix to a message. {{prefix}} - prefix (set as an option in a permission plugin), {{suffix}} - suffix (set as an option in a permission plugin), {{name}} - real name, {{displayname}} - display name
prefix="{{prefix}} {{displayname}}&f: "
# Sets the suffix to a message. {{prefix}} - prefix (set as an option in a permission plugin), {{suffix}} - suffix (set as an option in a permission plugin), {{name}} - real name, {{displayname}} - display name
suffix=" {{suffix}}"
# The weight of the template. A higher number will take priority over lower numbers when two templates could apply to the same player because they are in the both groups.
weight=10
}
Builder {
# The default colour for a player's chat if the "chatcolour" permission option isn't set on the player or group. Takes the same input as the "namecolour" option set to "" to retain default behaviour (no change of colour).
default-chatcolour="3"
# The default styles for a player's chat if the "chatstyle" permission option isn't set on the player or group. Takes the same input as the "chatstyle" option set to "" to retain default behaviour (no style).
default-chatstyle=""
# The default colour for a player's name if the "namecolour" permission option isn't set on the player or group. Takes the same input as the "chatcolour" option set to "" to retain default behaviour (no change of colour).
default-namecolour="3"
# Sets the prefix to a message. {{prefix}} - prefix (set as an option in a permission plugin), {{suffix}} - suffix (set as an option in a permission plugin), {{name}} - real name, {{displayname}} - display name
prefix="{{prefix}} {{displayname}}&f: "
# Sets the suffix to a message. {{prefix}} - prefix (set as an option in a permission plugin), {{suffix}} - suffix (set as an option in a permission plugin), {{name}} - real name, {{displayname}} - display name
suffix=" {{suffix}}"
# The weight of the template. A higher number will take priority over lower numbers when two templates could apply to the same player because they are in the both groups.
weight=15
}
Trainer {
# The default colour for a player's chat if the "chatcolour" permission option isn't set on the player or group. Takes the same input as the "namecolour" option set to "" to retain default behaviour (no change of colour).
default-chatcolour="7"
# The default styles for a player's chat if the "chatstyle" permission option isn't set on the player or group. Takes the same input as the "chatstyle" option set to "" to retain default behaviour (no style).
default-chatstyle=""
# The default colour for a player's name if the "namecolour" permission option isn't set on the player or group. Takes the same input as the "chatcolour" option set to "" to retain default behaviour (no change of colour).
default-namecolour=f
# Sets the prefix to a message. {{prefix}} - prefix (set as an option in a permission plugin), {{suffix}} - suffix (set as an option in a permission plugin), {{name}} - real name, {{displayname}} - display name
prefix="{{prefix}} {{displayname}}&f: "
# Sets the suffix to a message. {{prefix}} - prefix (set as an option in a permission plugin), {{suffix}} - suffix (set as an option in a permission plugin), {{name}} - real name, {{displayname}} - display name
suffix=" {{suffix}}"
# The weight of the template. A higher number will take priority over lower numbers when two templates could apply to the same player because they are in the both groups.
weight=5
}
DefaultTemplate {
# The default colour for a player's chat if the "chatcolour" permission option isn't set on the player or group. Takes the same input as the "namecolour" option set to "" to retain default behaviour (no change of colour).
default-chatcolour=""
# The default styles for a player's chat if the "chatstyle" permission option isn't set on the player or group. Takes the same input as the "chatstyle" option set to "" to retain default behaviour (no style).
default-chatstyle=""
# The default colour for a player's name if the "namecolour" permission option isn't set on the player or group. Takes the same input as the "chatcolour" option set to "" to retain default behaviour (no change of colour).
default-namecolour=""
# Sets the prefix to a message. {{prefix}} - prefix (set as an option in a permission plugin), {{suffix}} - suffix (set as an option in a permission plugin), {{name}} - real name, {{displayname}} - display name
prefix="{{prefix}} {{displayname}}&f: "
# Sets the suffix to a message. {{prefix}} - prefix (set as an option in a permission plugin), {{suffix}} - suffix (set as an option in a permission plugin), {{name}} - real name, {{displayname}} - display name
suffix=" {{suffix}}"
# The weight of the template. A higher number will take priority over lower numbers when two templates could apply to the same player because they are in the both groups.
weight=1
}
}
}
}
1 Like
Is it possible to add multiple commands for the warning system?
Something like this:
5 Warns: tempban {{name}} 2d Exceeding the active warning threshold (5).
10 Warns: tempban {{name}} 5d Exceeding the active warning threshold (10).
15 Warns: tempban {{name}} 10d Exceeding the active warning threshold (15).
20 Warns: ban {{name}} Exceeding the active warning threshold (20).
Duplication Bug
If a user has a blacklisted item (possession, environment, use all denied) in their hotbar, and they shift a different item (not blacklisted) into that spot of their hotbar, the item will duplicate. Here is a video of it in action: Dropbox - No photos or videos
Upon double checking that possession is denied it was found that the items (in this case eggs) they remain in the hotbar but disappear right away in the inventory. You can still duplicate items with it.
Minecraft: 1.10.2
SpongeAPI: 5.1.0-SNAPSHOT-b23f81b
SpongeForge: 1.10.2-2171-5.1.0-BETA-2006
Minecraft Forge: 12.18.3.2185
Nucleus-0.16.3-S5-1.10.2-plugin.jar
I can also submit an issue on the GitHub if you’d like of this issue.
Could you also change/edit something for the jail?
What would be good is when you jail someone they go to jail as normal, but when you unjail them it takes them back to their last location, can you make it so when you get unjailed you stay in the jail and then do /home or whatever?
This would be useful because say you are in a bad chunk and need jailing, you get jailed but when you get unjailed you would go back to that bad chunk and crash again ect (I know you can just fix the chunk or item that may have been causing it but this just would be a nice feature.
@popcorn1111 I’ll get back to you on that - it looks OK so I’ll have to test this more closely.
@Txk Nope, not as it stands, but it is likely that I’ll either work on that in a future release, or I might create some add-on that is outside of Nucleus proper that has a more full featured punishment system.
@sheogorath Thanks, I think I know why that happens, I’ll fix it ASAP, though I may as well take the time to restructure a couple of things. I’ve put it onto GitHub, thank you for your help!
Using jail in this way is broken behaviour, really. Others have asked for this, instead, you can use /spawn other <name> on offline players and they will log in at spawn. That way, you don’t have to mess about with jailing and unjailing and the player can get back on very quickly. 
Alright, will give it a go, thanks!
Still having the issue 
Sorry for delay - Christmas and all 
Didn’t work with 1.10.2 2171 5.1.0 B 2008, and just seen one was released within last few hours so will update to that as well.
Everything else should be the same save Nucleus being 0.16.3 S5 and PEX build 146 now.
Did you update Forge? Are you running build 2171?
I replied to this on the issue you submitted on GitHub for my previous post but:
I get an error upon trying to build it? p_p
[link removed]
./gradlew clean build
So I tried running the debug for LuckPerms and it is coming back true.
It seems to work fine on the first login, but once you log out and try to log back in it breaks.
I’ll have to investigate, but as I haven’t touched that part of the code for a while, this is very odd as it wasn’t broken before, and isn’t broken for me now. I’m not overly familiar with LP, it does some very ambitious things that sometimes do things we’re not expecting. I need to test it.
Just had a look and a play, and the config looks fine. Indeed, when using my PEX based setup, I can set and unset the chatcolour option for a player, and it’ll do the right thing with the colours. I’d have to setup PM on my machine, as I need to do with LP.
2 Likes
@IBG_Nova Strange bug, but I’ve replicated it - I would argue it’s a problem in LuckPerms. I’ll file an issue on LP’s repo. I’ll look into creating a workaround too.
Edit: Filed the issue
Edit 2: I’ve also worked around it, should work when I push the next update, which I plan for tomorrow,
2 Likes
is there a possibility of editing messages?
Thanks,
Charles Berkley