Pass/fail summin skill

[k0r3l1k]

Does anyone know of a way to make a summon skill only cast able if one or more stats have value X or above?

[jetaman]

I think that's very easy to do with condition formula.

[k0r3l1k]

This issue is no longer relevant to my plans. For the record I will say that summon skill or not, I don't know of a way to lock out a skill from being cast via formulas.
To my knowledge it is impossible, and this is something I have spend a great deal of effort investigating.

[jetaman]

It is very much possible: i've seen it a lot in MedianXL. For example, when you use morph, it allows only the use of melee skills. Or there are three uber skills at level 90, you choose one, and two others are blocked. Or as a paladin, you choose Holy or Unholy build, if you choose one, the other is blocked.
You can get the files and look how it is used. Brother Laz released his txt files in his last version. Would you like to look in the files?

[k0r3l1k]

Those all use skpt column to lock out access to the learning the skill. There is no way to lock out the casting of a learned skill.

Regarding transformations, it is possible to lock out certain skills when the player is affected by or not affected by certain states, but how those states are applied/removed becomes an issue itself.

My purposes require a simple stat comparison to enable/disable the skill. As said above the topic is purely academic at this point, as I no longer need it for the purpose of my skill design.
However, I did get an add-on from kingpin which allows formula for mana cost, however that add on is no longer compatible with my mod, so it cannot be used here.

The above statements refer to vanilla.

Edit:
Sorry form my atrocious grammar here, writing on my phone doesn't make for fluent sentence structure.

Also, I am not trying to be argumentative or arrogant. I really would like to know a trick to do this and my comments are meant to clarify what I was seeking to do.

Additional comments or ideas are very welcome on the topic.

[Vav]

Those all use skpt column to lock out access to the learning the skill. There is no way to lock out the casting of a learned skill.

Regarding transformations, it is possible to lock out certain skills when the player is affected by or not affected by certain states, but how those states are applied/removed becomes an issue itself.

My purposes require a simple stat comparison to enable/disable the skill. As said above the topic is purely academic at this point, as I no longer need it for the purpose of my skill design.
However, I did get an add-on from kingpin which allows formula for mana cost, however that add on is no longer compatible with my mod, so it cannot be used here.

The above statements refer to vanilla.

Edit:
Sorry form my atrocious grammar here, writing on my phone doesn't make for fluent sentence structure.

Also, I am not trying to be argumentative or arrogant. I really would like to know a trick to do this and my comments are meant to clarify what I was seeking to do.

Additional comments or ideas are very welcome on the topic.

The only thing I can really think of, have you tried using the stat as the amount of summons allowed? For example in skills.txt set the max summon column to 0, then use a condition formula so if you have a specific stat it gives you the correct amount of max summons.

[HarvestWombs]

The only thing I can really think of, have you tried using the stat as the amount of summons allowed? For example in skills.txt set the max summon column to 0, then use a condition formula so if you have a specific stat it gives you the correct amount of max summons.

We already tested that, the petmax will always default to 1.

[Vav]

The only thing I can really think of, have you tried using the stat as the amount of summons allowed? For example in skills.txt set the max summon column to 0, then use a condition formula so if you have a specific stat it gives you the correct amount of max summons.

We already tested that, the petmax will always default to 1.

That's unfortunate, I am afraid the only thing I can think of you can really do at this point softcode wise is use a stat check formula on the delay / cooldown, of course this will still allow them to cast it once before the massive cooldown kicks in to lock it out, so its not a proper solution.