OfficialJaco
Feel free to share ;)
:D Agreed.
Damage to twig onlySolved
As written in currently, it does also require the AuthorizedDamage flag to be set. This is the one that allows the owner to also destroy his own twig anyway, among other things.
Also, it's great that you can get paid work done on plugins. But, not everyone can. Anyway, this should not be the place to advertise other options as this is the discussion forum for TruePVE.
Also, it's great that you can get paid work done on plugins. But, not everyone can. Anyway, this should not be the place to advertise other options as this is the discussion forum for TruePVE.
Also a reminder that the Patch option is there for other developers to contribute patches to help, else I'm sure maintainers and plugin developers would always appreciate a little bit given back to them for their work that others often take advantage of.
rfc1920
As written in currently, it does also require the AuthorizedDamage flag to be set. This is the one that allows the owner to also destroy his own twig anyway, among other things.
Also, it's great that you can get paid work done on plugins. But, not everyone can. Anyway, this should not be the place to advertise other options as this is the discussion forum for TruePVE.
So, IF I set it to AuthorizedDamage, AND TwigDamage, Others can deal damage to MY Twig only Correct? I just want to get that straight?
EDIT: I dont remember seeing where it said that in the overview til just now when I read it over again. :D I'll do this.
Yes, I just added that note into the documentation because I realized it was left out. Note that AuthorizedDamage alone wouldn't allow twig damage for anyone but the owner. So, TwigDamage was applied as an elevation to that. It could be handled separately but perhaps an equal number of users would find that as annoying as how it was done currently.
And, yes, it is only an elevation to allow twig to be damaged. There are other ways to handle this, I'm sure. But, decay plugins generally won't touch it if the TC is stocked. So, this is one solution for PVE servers.
And, yes, it is only an elevation to allow twig to be damaged. There are other ways to handle this, I'm sure. But, decay plugins generally won't touch it if the TC is stocked. So, this is one solution for PVE servers.
Yes, I just added that note into the documentation because I realized it was left out. Note that AuthorizedDamage alone wouldn't allow twig damage for anyone but the owner. So, TwigDamage was applied as an elevation to that. It could be handled separately but perhaps an equal number of users would find that as annoying as how it was done currently.
Awesome, And yes it works perferctly. I dont mind it this way.... But having Authorized Damage and Removertool is kinda redundant. But At least they have 2 options. In the future, think it will ever be seperate ?
Well, AuthorizedDamage was added before I took over. It was definitely helpful to return twig and other damage to the owner. If the server does not have RemoverTool, then I guess you're just stuck with that twig until it decays along with whatever wood pieces you had. Twig should probably be part of a ruleset. But, that will require some rework to how those rules are read, and probably with some negative consequences.
Well, AuthorizedDamage was added before I took over. It was definitely helpful to return twig and other damage to the owner. If the server does not have RemoverTool, then I guess you're just stuck with that twig until it decays along with whatever wood pieces you had. Twig should probably be part of a ruleset. But, that will require some rework to how those rules are read, and probably with some negative consequences.
The main reason why I ever wanted twig to be destroyed is because people build twig to fight heli on my server.
I just tested my current settings, NoHeliDamage (Which i also have in the Ruleset) is not allowing the heli to damage to a twig base.
These are my Flags for the "Default" Ruleset:
"flags": "NoHeliDamage, HumanNPCDamage, LockedBoxesImmortal, LockedDoorsImmortal, AdminsHurtSleepers, TrapsIgnorePlayers, TurretsIgnorePlayers, SelfDamage, AuthorizedDamage, TwigDamage",
EDIT: I did just read the overview on the "TwigDamage" flag that said players can Damage, but I believe that in the update section it said "anything". Is this going to be possible without having all buildingblock tiers damagable from heli? At least though, I'm one step closer to my goal in getting the Twig Damagable. :D
Also, it's great that you can get paid work done on plugins. But, not everyone can. Anyway, this should not be the place to advertise other options as this is the discussion forum for TruePVE.
I made this post 11 months ago and am still waiting on a solution so I don't see what the issue is with him sharing a solution to my problem?
I made this post 11 months ago and am still waiting on a solution so I don't see what the issue is with him sharing a solution to my problem?
I think it was more of no solution was being offered to share or contribute toward the original, just that he had paid someone else who did it. Also keep in mind this plugin has had multiple maintainers, with very little given back I'm sure.
I think you guys (especially wulf) have me gravely mistaken. I was offering the PLUGIN DEVELOPER the fix I had made so he could push it out. Had nothing to do with anything else. My god, I disappear for 3 days to deal with this update/oxide mess nuking all my servers and I take a peek this morning and see all this talk about me doing this and doing that. I was simply trying to let the TruePVE guy know if he wanted the fixed version to just PM me. If anything just to see how we did it.
You guys are so quick to jump to negative conclusions around here. How about we get that "Failed to compile" stuff fixed with Oxide instead ;)
You guys are so quick to jump to negative conclusions around here. How about we get that "Failed to compile" stuff fixed with Oxide instead ;)
If the 'fix' was sent to me then I must have missed it. Otherwise, I'm certainly not going fishing for it. tbird, I see a lot of posts here and there from people saying they got whatever fixed elsewhere without offering, or recommending another plugin to fix it. It's easy to just lump those together. I don't think it's anything particular about this forum, although the community does have its peculiarites from time to time. Generally, what is recommended is to either send a patch using the patch tool or even a full version by PM if you're unable to run diff.
tbird412
I think you guys (especially wulf) have me gravely mistaken. I was offering the PLUGIN DEVELOPER the fix I had made so he could push it out. Had nothing to do with anything else. My god, I disappear for 3 days to deal with this update/oxide mess nuking all my servers and I take a peek this morning and see all this talk about me doing this and doing that. I was simply trying to let the TruePVE guy know if he wanted the fixed version to just PM me. If anything just to see how we did it.
You guys are so quick to jump to negative conclusions around here. How about we get that "Failed to compile" stuff fixed with Oxide instead ;)
Sorry if you got the impression that it was negative, but it was just a reminder that developers here often get very little in return. It's easy to pay someone else to do something when you want it done, but it's also easy to forget about those that make a lot of what server owners use possible.
As mentioned as well, developers can contribute any "fixes" to current maintainers, but I didn't see that being offered, only that you paid someone to do it quicker.
Not aware of any "failed to compile" issues, but anything dealing with the old compiler isn't really being developed any further due to complications and limitations.
Thank you. Twigs damage works perfect.
Locked automatically