• Please note: In an effort to ensure that all of our users feel welcome on our forums, we’ve updated our forum rules. You can review the updated rules here: http://forums.wolflair.com/showthread.php?t=5528.

    If a fellow Community member is not following the forum rules, please report the post by clicking the Report button (the red yield sign on the left) located on every post. This will notify the moderators directly. If you have any questions about these new rules, please contact support@wolflair.com.

    - The Lone Wolf Development Team

Armor counts as light

F

Frodie

Well-known member
I have an Armor that is not in the "Light Armor" category, but it counts as light for pre-reqs on feats, abilities, etc.

So I added at pre-levels 10000

Code: 
perform container.assign[ArmorClass.Light]

Loads fine, but it will not tag the armor after it's on the hero. So I think it's timing, but can't seem to find the right match. Any ideas?

Thanks again yall!
 
Yea, on the armor it's self. I was thinking the container is where the issue is. But I added this to a mech and it works

Pre-Levels 10000

Code: 
foreach pick in hero from BaseArmor where "ArmorGroup.FGMPSimple"
  perform eachpick.assign[ArmorClass.Light]
nexteach

So all cool. Thanks again yall!
 
How many armors is this going on? If it's just a couple I'd just use this on the individual armors instead of wasting the computing power on a loop.

Code: 
  perform assign[ArmorClass.Light]
 
Make sure you test that it works right when one of these armors is used to create a custom armor.
 
I spoke too soon, lol.
I realized I needed also needed the feat "Armor Proficiency (Simple)" to count as "Armor Proficiency (Light)", so easy enough, went to the feat and check Feat Counts As: Armor Proficiency (Light). Check to make sure the tag was on the hero, and it was. So went to make sure it met the pre-reqs on a feat that need Armor Proficiency (Light), like arcane armor feat. And it doesn't. So let me look into the arcane armor and see what it is looking for.

Oh, I see, it's looking for tagis[Hero.ProfLight] <> 0. Hum, I need to find a way to tag the hero with that, but not be proficient in light armor.
 
Last edited:
Frodie said:
Oh, I see, it's looking for tagis[Hero.ProfLight] <> 0. Hum, I need to find a way to tag the hero with that, but not be proficient in light armor.
Click to expand...
I guess you could try setting Hero.ProfLight REALLY late in timing so that the validation scripts find the tag but the check to make a character proficient with armor has already happened.
 
Yes and no, it gets rid of the pre-req, but they gain the light armor. So a no go. Tried final and render, but still no. I wonder if a loop would help? Uhg, the one time I wish timing mattered, lol.
 
Frodie said:
Yes and no, it gets rid of the pre-req, but they gain the light armor. So a no go. Tried final and render, but still no. I wonder if a loop would help? Uhg, the one time I wish timing mattered, lol.
Click to expand...
You tried Render/999999999? That should put you just before Validation. OR actually try Validation/1
 
Ok, Validation/1 works, it will not "grey out" the armor but it does say you aren't proficient. So that will have to work. Thanks yall!
 
This sort of thing - altering tags in the Render or Validation phase - is a big hack, and really vulnerable to future changes. What exactly are you trying to accomplish, so that we can find a better way to do this? I'm guessing based on the script in your first post that this is somewhat similar to the mithral material, but how does it differ from how mithral works, to make the armor lighter for everything but proficiency.

And if it is just mithral, but for proficiencies too, isn't that the same as elven chain?
 
Basically, the 3pp want's 2 sets of armor proficiency, or new categories. They are basically the same but one is "archaic" and the other is "modern" (with an extra category for simple armor). I got it to mechanically to work with the "ArmorGroup" tags. The issue came when feat's like Arcane Armor Training looking for the Hero.ProfLight tags.

ATM - it works, but I could do a loop, it you think that would be more stable.

I thought of a loop like this on the Modern feats, (I just re-named the core feats and added archaic in front).

Code: 
Render/999999999

perform hero.assign[Hero.ProfLight]


Code: 
PreLevels/10000

foreach pick in hero from BaseArmor where "ArmorClass.Light"
    perform eachpick.delete[Helper.Proficient]
nexteach


So I have all the categories working, but the pre-req in feats and abilities will not work for the modern armor groups.

Is there a tag like HasHero?
 
Last edited:
Whether a particular piece of armor is something that this character is proficient in is recorded by adding the Helper.Proficient tag to that armor at Pre-Level/10000 (the script is named "Assign Armor Proficiency"

So I'd recommend a foreach through all the armors that this applies to, adding that tag. Ignore light/medium/heavy - they have no relation to the rule you're implementing.
 
Oh, and if you're deleting Helper.Proficient, work at Pre-Levels/10100, or some other time AFTER pre-levels/10000, not at the same time, or it's random whether the Helper.Proficient tag will have been added yet before your script deletes it, or whether your script will delete a non-existent tag (meaning nothing happens), and then the other script will add it.
 
Cool, Thank You! Yea, I have the feats pick the correct armor, the issue is the feat has to mimic the similar feat for pre-req issues, (in the case of simple armor I needs to count as light armor, but not be light armor).
 
Last edited:
Mathias said:
Whether a particular piece of armor is something that this character is proficient in is recorded by adding the Helper.Proficient tag to that armor at Pre-Level/10000 (the script is named "Assign Armor Proficiency"

So I'd recommend a foreach through all the armors that this applies to, adding that tag. Ignore light/medium/heavy - they have no relation to the rule you're implementing.
Click to expand...
If I understand this all correctly. This part Frodie has done. His issue is that Medium Armor "Feat" need to SEE that the character has Light Armor Proficiency.

So other feats like Arcane Armor is doing this as a Pre-Req:
Code: 
tagis[Hero.ProfLight] <> 0

Which is why I said to add the tag at Validation/1 to a) Make feats like Arcane Armor THINK we have Light Armor Proficiency without actually causing ALL Light armor to be proficient.

If the base feat was changed to use the "Feat Count As" logic then Frodie wouldn't have to do the 'Hack' as you called it. :)

So in this case maybe Frodie you would be better off putting this in as a "BUG" and wait for LW to change the Armor Feats... ;) :D
 
You must log in or register to reply here.
Back
Top