Mr01sam
-
Posts
1,406 -
Joined
-
Last visited
Content Type
Profiles
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by Mr01sam
-
That's possible, I'll double check that scenario. Another thing to note is that the protection damage timer will be ignored if the plugin is reloaded or the server is reset.
-
Changed Status from Pending to Work in Progress
-
I just tried to reproduce the error you described, but it is not happening for me. This is what I attempted: Have TC setup with offline only protection, 1 second delay for offline protection and 30min delay for damage Owner is online, the base is unprotected, the base takes damage Message says that protection will be delayed because of the damage Owner goes offline, but the protection doesn't start until after damage timer finishes (30min) I have not been able to get it to say both "Protected" and "RecentlyTookDamage" at the same time. Would you mind sharing your config with me so I can debug it further?
-
Quality Crafting works by storing the data in the item text, if his plugin is accommodating that, the it should be working... So I'm not quite sure what's going on there
-
Like other plugins, it uses normalized rgb. For example, the color red would be "1.0 0 0 1", that is, red, green, blue, alpha. -
What you mentioned is not a feature, directly. But since the protection is perm based, you could combine this with another plugin to revoke protection. That being said, there are numerous options included to make it so you are raidable. For one, protection (if configured this way) costs something, if you don't have that resource, you don't get protection. Second, there's an option to charge per damage taken, if you use this option it can make it so that even if you have 100% protection, other players can "bleed" your protection balance by dealing enough damage. You can also opt to not set 100% protection and instead do say 50% or something. Tons of options to balance around. -
I'll look into this in the future!
-
@Cabra You can add more protection levels in the config file, please see the protection levels section of the documentation
-
@Jakub Rosner I'm not sure how you got the config file to generate with a version of 0.0.0. However, if a simple fix is to just update your config version property to be 3.1.0, it should then accept it as valid.
-
Unfortunately, there's no config option for that, but I can show you what you need to edit in the code if you message me.
-
Yup just saw your message! I added API hooks in 3.1.0, I just gotta add them to the documentation!
-
Changed Status from Work in Progress to Closed Changed Fixed In to 3.1.0
-
I'm sorry but that's not in my scope of this plugin, that sounds like it could be its own plugin entirely.
-
No, it will just disable the built in indicator (the shield).
- 273 comments
-
- 1
-
-
- #protection
- #base
- (and 5 more)
-
Yes, you can disable that shield indicator in the indicator settings section of the config. Just set "Enabled" to false.
-
No problem!
-
Changed Status from Work in Progress to Closed Changed Fixed In to 3.1.0
-
Added in v3.1.0
-
Changed Status from Pending to Closed Changed Fixed In to 3.1.0
-
Upgrade to v3.1.0, this is fixed in that version!
-
Changed Status from Pending to Not a Bug Changed Fixed In to 3.1.0
-
I understand your frustration, it wasn't intentional to do just foundations in the first place, as the original version of raid protection took both floors and foundations into account. In addition, I did not want to separate them out as all the calculations would have to be rewritten and it adds more complexity to the UI/config ect. Here's a first things you could do. Lower the price charged per floor, realistically, if you cut the price in half - it should equate to the same amount as before for single story buildings (keep in mind there was a bug in v3.0.0 that made it so triangle foundations didn't count at all). If you find that's still too expensive, lower it even further. Disable the option If you message me, I'd be willing to show you how to make the necessary change in the code to revert this specific change. Note that if I do this, you be be responsible for changing it yourself again in future updates. That being said, I highly recommend trying option 1, if not I'd be happy to help.
-
Changed Status from Pending to Not a Bug Changed Fixed In to 3.1.0
-
Yes your config file is outdated as of v3.1.0, I recommend you make a backup of it (for reference) and then delete the original copy so that the plugin generates a new one. Then manually transfer your settings over. If you're unsure what to do, see the section of documentation for "Upgrading Versions"
-
Awesome, glad to hear it man!
