Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Condition Mechanical Free Death #2

Open
pquerner opened this issue Oct 17, 2017 · 4 comments
Open

Condition Mechanical Free Death #2

pquerner opened this issue Oct 17, 2017 · 4 comments
Assignees

Comments

@pquerner
Copy link

pquerner commented Oct 17, 2017

Can you find out if your mechanical pet has a free death in a condition?
Example

ability(282) [self.hp <= 375 & !self.freedeath.available] # (only self destruct if free death not available)
@pquerner
Copy link
Author

I guess you could just use this
[ ! enemy.aura(1420).exists ]

to find out if cheat death already procced.

@axc450
Copy link
Collaborator

axc450 commented Apr 12, 2020

Ill add this, possibly as [self.revived]

@axc450 axc450 self-assigned this Apr 12, 2020
@patf0rd
Copy link

patf0rd commented Apr 16, 2020

Hello, I don't see a point in replacing one condition with another. Years ago I asked the devs to somehow make it visible in the interface if Failsafe was triggered and luckily they added the cogwheel icon and Mechanical aura we can check with scripts, so I think [ self.aura(Mechanical:244).exists ] is the way to go and we can even check for non-active player pets. Of course, there could be specific conditions for tons of situations like undead passive triggered, survival triggered etc. to spare some characters in the scripts but why overload the code for such a small benefit?

@axc450
Copy link
Collaborator

axc450 commented Apr 16, 2020

self.revived would apply to all revivable mechanics.
I dont think its a code bloat - in fact its a direction I want to take the language in.
Pretty much everything that is common should have a custom function for to keep scripts clean.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants