-
Notifications
You must be signed in to change notification settings - Fork 23
Badges
This plugin should be enabled if you're using the "Player Badges" mod from the workshop. It overrides the plugin's functions for determining admins so it reads from Shine's user config instead of the default NS2 file.
It has no config or commands, just enable it if you want the player badges to read from Shine's users.
To assign a badge to a group, add either a "Badge"
field, or a "Badges"
field to the group's data. For example:
"SuperAdmin": {
"IsBlacklist": true,
"Immunity": 100,
"Commands": [],
"Badges": [ "crown", "heart" ]
},
"Admin": {
"IsBlacklist": false,
"Immunity": 50,
"Commands": [ "sh_kick", "sh_ban" ],
"Badge": "heart"
}
You can also assign badges to users individually. It works the same as for groups, except you add the "Badge"
or "Badges"
entry to a user's data entry.
"123456": {
"Group": "SuperAdmin",
"Badge": "nyancat"
},
To assign badges to rows, use the following format for the "Badges" table:
"Badges": {
"1": [
"nyancat",
"heart"
],
"2": [
"unicorn",
"marine"
]
}
where the number index is the badge row, and each row contains a list of badges in it. You can assign up to 10 rows, with 5 being the middle (default) row.
If you want to always have certain badges live on certain rows, you can set a master table of badge rows in UserConfig.json
as follows:
{
"Badges": {
"1": [
"badge1", "badge1b"
],
"2": [
"badge2", "badge2b"
],
"3": [
"badge3"
]
},
"Groups": {
"ExampleGroup1": {
"Badges": [ "badge1", "badge2" ],
...
},
"ExampleGroup2": {
"Badges": [ "badge1", "badge3" ],
...
},
...
},
...
}
In this example, ExampleGroup1
will have badge1
on their first row, and badge2
on their second, while ExampleGroup2
will have badge1
on their first row and badge3
on their third row.