-
Posts
3,405 -
Joined
-
Last visited
Content Type
Profiles
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by Steenamaroo
-
IssueRewardsAtWipe: Where to set rewards?
Steenamaroo replied to ChardaZAR's Support Request in Support
Hi, Those two settings to govern rewards are in the main PlayerRanks.json config file, but you set up the rewards tehmselves in the PlayerRanksRewards.json file. It's a separate file. Rewards must be viable console commands, comma separated, and you can use {id} as a place holder for player steam ID. -
No, not /server/YourServerName/cfg That's a different folder and should have your four pictured .cfg files in it. You're looking for /server/cfg If it doesn't exist create it and put all the AI stuff in it. For clarity /server/YourServerName/cfg should contain three or four cfg files. /server/cfg/ai should contain thirty something AI related files
-
Hi, Sounds like you're missing files from /server/cfg/ai BotReSpawn doesn't actually use the files from there so it *should* be inconsequential, but if scientist_roam is missing (as the error suggests), other npc or animal AI files might be missing too. Re-update your server, or grab a copy of that /server/cfg/ai folder from a backup or another install.
-
Hi, Thanks for reporting. I think the content of PlayerRanksDelayedRewards.json is becoming null some how. Deleting that file then reloading the plugin should clear the error. Please let me know if that's the case ^ I'll try and find out what caused it and prevent it from happening in future versions.
-
There's the answer. "Config file issue detected. Please delete file, or check syntax and fix." Delete your /config/PermissionsManager.json then reload the plugin.
-
Hi, Everything you're saying suggests the plugin isn't loaded. Redownload the plugin from codefling and copy it in to your server's oxide or carbon plugins folder. Watch your server console while you're doing this - It should confirm that the plugin loaded. If there are any errors at this stage there's either something wrong with the plugin file or an existing config or language file. Paste the error here, in that case.