Removing a Type ability? - Page 2

EightBitz · August 29th, 2017, 11:23 AM

Quote:

Originally Posted by Aaron

The way types work is kinda arcane, used to be all full types were on all heroes and only one was activated. Switched it over to them all being bootstrapped by certain types of picks, but with a match expression so they only become live when the correct tag is present. Thus, I am guessing your created race only has the tag portion, and wasn't also bootstrapping the new type.

Please give NoTypeAbil a try first.

I have multiple creatures that have these two things in common. They are aberrations, and they do not have darkvision. The whole point of having a type is so I don't have to reinvent the wheel with each creature.

Would pHideAbility work? And can you give me the syntax?

Aaron · August 29th, 2017, 11:47 AM

There are at least 150 monsters which have similar exceptions to what their type or subtype normally grants, and this is the method by which we handle that. If you'd prefer to do it differently, by making a new type, do what you gotta do. It just doesn't seem like a good idea to me to have 5 different versions of a type, each of which is slightly different and all of which are supposed to count as each other for pre-reqs and so on.

I don't think hiding the darkvision pick is a good idea, because what if some other source needs to add a new darkvision? Only one is ever shown, and if you hide that, new copies will remain in the background, hidden from the user. Which will be confusing and distressing. "Why aren't my googles of darkvision working! Better send a bug report to HL", and then I have to figure out that there is a 3rd party file they are working with and that it is doing something unusual.

EightBitz · August 29th, 2017, 12:12 PM

Quote:

Originally Posted by Aaron

I don't think hiding the darkvision pick is a good idea, because what if some other source needs to add a new darkvision? Only one is ever shown, and if you hide that, new copies will remain in the background, hidden from the user. Which will be confusing and distressing. "Why aren't my googles of darkvision working! Better send a bug report to HL", and then I have to figure out that there is a 3rd party file they are working with and that it is doing something unusual.

I understand your point here, but these aren't player races. These are creatures. This is akin to debating the merits of a cow not being able to use weapons. The point is moot because a cow is not a player race.

Anyway, I don't want to belabor the point anymore than I have.

Aaron · August 29th, 2017, 12:48 PM

I like to customize my monsters quite a bit, so it seems important to me, but like I said, I am only giving advice so do as you feel is best.

ShadowChemosh · August 29th, 2017, 12:55 PM

Quote:

Originally Posted by Aaron

The way types work is kinda arcane, used to be all full types were on all heroes and only one was activated. Switched it over to them all being bootstrapped by certain types of picks, but with a match expression so they only become live when the correct tag is present. Thus, I am guessing your created race only has the tag portion, and wasn't also bootstrapping the new type.

Please give NoTypeAbil a try first.

NoTypeAbil.tpAberr will also remove the class skills. I just tested this out on a custom race that is an aberration.

Looking at the Darkvision scripts it appears a tag of "Hero.NoTypeDaVi" exists that is designed to disable Darkvision added by types. I just tested and it works fine.

Add the following script to your monster:

Pre-Levels/1000

Code:

~ Disable darkvision from aberration type
perform hero.assign[Hero.NoTypeDaVi]

EightBitz · August 29th, 2017, 01:06 PM

Quote:

Originally Posted by ShadowChemosh

NoTypeAbil.tpAberr will also remove the class skills. I just tested this out on a custom race that is an aberration.

Looking at the Darkvision scripts it appears a tag of "Hero.NoTypeDaVi" exists that is designed to disable Darkvision added by types. I just tested and it works fine.

Add the following script to your monster:

Pre-Levels/1000

Code:

~ Disable darkvision from aberration type
perform hero.assign[Hero.NoTypeDaVi]

Perfect! Thank you very much!

Aaron · August 29th, 2017, 01:27 PM

Quote:

Originally Posted by ShadowChemosh

NoTypeAbil.tpAberr will also remove the class skills. I just tested this out on a custom race that is an aberration.

Looking at the Darkvision scripts it appears a tag of "Hero.NoTypeDaVi" exists that is designed to disable Darkvision added by types. I just tested and it works fine.

Add the following script to your monster:

Pre-Levels/1000

Code:

~ Disable darkvision from aberration type
perform hero.assign[Hero.NoTypeDaVi]

Yep, Class Skills are a subset of "everything". Looks like I missed that memo, learn something new every day.

Aaron · August 29th, 2017, 01:29 PM

Also, looking at how it is used, I don't think you need an eval script to assign it. If you create the monster with the tag present, it should be forwarded automatically FYI.

ShadowChemosh · 01:38 PM

Quote:

Originally Posted by Aaron

Also, looking at how it is used, I don't think you need an eval script to assign it. If you create the monster with the tag present, it should be forwarded automatically FYI.

Hero tags are forwarded automatically? Didn't know that.....

Thanks Aaron. Yep just adding the tag to the race also caused Darkvision to be removed without needing the script.

Aaron · August 29th, 2017, 04:01 PM

Only certain Hero tags added to a race are forwarded automatically, it looks like that is one of them.

Aaron Senior Member Join Date: Oct 2011 Posts: 6,793 August 29th, 2017, 12:48 PM	I like to customize my monsters quite a bit, so it seems important to me, but like I said, I am only giving advice so do as you feel is best.
#14