Mr01sam
-
Posts
1,245 -
Joined
-
Last visited
Content Type
Profiles
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by Mr01sam
-
You have to add a new entry to your lang file for every new mode you add for every spot you see the default modes. So in the WarMode.json lang file, you need to add the following entries: "mode rogue" "ss title rogue" "ss text rogue" And if you add other custom modes in the future, you'll need to do the same for those as well. Additionally, if you're using the spawn ui, you will need to edit the WarModeSpawnUI.json lang file as well. And add the following values "rogue" "rogue info"
-
Changed Status from Pending to Gremlins
-
Popup Attack Indicator block from distamce/when flying
Mr01sam replied to Bear Grills's Support Request in Support
Changed Status from Pending to Gremlins -
Popup Attack Indicator block from distamce/when flying
Mr01sam replied to Bear Grills's Support Request in Support
Just curious, if you don't want them to do that, then why not just disable the popup indicator? -
Changed Fixed In to 1.2.7
-
Changed Status from Pending to Closed Changed Fixed In to 1.2.7
-
Changed Status from Pending to Not a Bug
-
Try the newest version of simple status that was just uploaded - v1.2.7. Let me know if it does or doesn't fix your issue. -
Are you using carbon or oxide?
-
Ah yeah, if you have other pve addons they might conflict with each other - you'd have to make sure they are set up in such a way that they will not conflict. For the raidable bases, you just need to install the raidable bases plugin and you should see the options for it on the right hand side in the admin panel UI.
-
Which things are you referring to? I recommend downloading and utilizing the Admin Panel extension plugin. Give yourself the warmode.admin permission and use it with the /warmode.config command. You will get a UI that will allow you to configure rules for each mode. If you want to make PVE protected from everyone then you will want to set everything to "false" for each mode. Read the descriptions of each of these rulings, it will explain what you are setting.
-
Hey, can you send me your lang file(s)?
-
Changed Status from Pending to Not a Bug
-
You can use the GetDuration method for this. If the value returned != 0, then the player has that status. For statuses that have an unlimited duration, it will return a max value integer.
-
Changed Status from Pending to Not a Bug Changed Fixed In to 1.2.0
-
Yes, this has been updated, since there can be more modes than just pvp and pve now, you now need to specify what mode it is being forced to, like this for example: "ForceModeInZone": { "14631241": "pvp", "57476821": "pvp", "42412954": "pvp", "54590812": "pvp", "26034994": "pvp", "56384445": "pvp", "34877606": "pvp", "73330248": "pvp", "51977381": "pvp" } Sorry for the confusion 🙂
-
Changed Status from Work in Progress to Closed
-
Changed Status from Pending to Closed Changed Fixed In to 1.2.0
-
Should be fixed in 1.2.0, make sure you get the latest SimpleStatus as well.
-
Hey sorry, if your plugin is broke for 1.2.6, I'm adding the OnSimpleStatusReady hook back. Sorry for the inconvenience! -
Changed Status from Pending to Not a Bug
-
It would require someone to develop it, but this could definitely be integrated with NoEscape!
-
In the next update there will be 🙂 -
I'm currently working on a big update that releases soon, we should see if you still see this problem after the update.
-
No plans currently to include that - but like you said you can do that through commands (or just manually editing the config) maybe in the future I can include it as an extension plugin!
