Event_setInvincible & Event_setCantDamage

[chrisbot6]

Actually the main problem here is that the boolean must be put onto the player as true onSpawn or the mod won't function properly and break damage altogether. See my modification of the event for how I sorted that out.

[Ad Bot]

[-Jetz-]

Actually the main problem here is that the boolean must be put onto the player as true onSpawn or the mod won't function properly and break damage altogether. See my modification of the event for how I sorted that out.

Yes, that would be a problem if done improperly, and yes there is a way to handle that, which you did. Gold star. The bigger problem though is that the author stubbornly refuses to acknowledge the issue. Yes it is minor, and maybe it doesn't warrant a rerelease of the simple add-on, but denying the error completely is stupid.

[Mysteroo]

Oh no, he made an event with weird wording, all of Blockland is going to tend towards disorder because of this, burn him at the stake

99% of everyone isn't going to care if the event says 'can' or 'can't.' It's not hard to use 2% of your brain power to decipher what setcantdamage-true/false means

[Electrk.]

Oh no, he made an event with weird wording, all of Blockland is going to tend towards disorder because of this, burn him at the stake

99% of everyone isn't going to care if the event says 'can' or 'can't.' It's not hard to use 2% of your brain power to decipher what setcantdamage-true/false means

did you read the whole topic

[Nobot]

did you read the whole topic

yeah and it's pretty much people pushing opinions onto OP
I personally think the event normally is fine (aside from what chrisbot said)

OT: cool event, will probably use this

[Mrmii21]

onwhatever > Player > setInvincible [  ]

Wait, isn't this already possible with the invincible playertype?

onX > Player > changeDataBlock > Invincible Player

[Nobot]

Wait, isn't this already possible with the invincible playertype?

onX > Player > changeDataBlock > Invincible Player

yes

[-Jetz-]

Oh no, he made an event with weird wording, all of Blockland is going to tend towards disorder because of this, burn him at the stake

99% of everyone isn't going to care if the event says 'can' or 'can't.' It's not hard to use 2% of your brain power to decipher what setcantdamage-true/false means

yeah and it's pretty much people pushing opinions onto OP
I personally think the event normally is fine (aside from what chrisbot said)

Think of it as informing someone that "ain't" is not a word. Yes you can understand them just fine if they say it, but it's wrong and sounds dumber than the alternative.

[Nobot]

Think of it as informing someone that "ain't" is not a word. Yes you can understand them just fine if they say it, but it's wrong and sounds dumber than the alternative.

only SetCan'tDamage isn't necessarily classified as "wrong" because it "sounds funny"
Seems to me like you guys are pushing this thing a little too far.

[-Jetz-]

only SetCan'tDamage isn't necessarily classified as "wrong" because it "sounds funny"

The ideas behind good practice disagree.

Seems to me like you guys are pushing this thing a little too far.

Perhaps. I'd much rather prefer this topic just die over debating this much longer.

[Peejster]

Wait, isn't this already possible with the invincible playertype?

onX > Player > changeDataBlock > Invincible Player

Yes, but then you run into the issue of having players with jets in a mini where they shouldn't have them, blockheads in a horse-only minigame, etc. Changes like this just work better if they don't end up replacing the player's playertype. A set of armor items on RTB got rejected for this very reason, even.

As for event names, I would suggest SetPacifist as a substitute.