Custom Tag Expression for Simple Weapons

[smokeh]

Edit: In the end, I was going to have the weapons chosen be added to a minion, but I forgot that an eval script can't add a pick. I'm still interested to see why my list below wasn't working. I'm going to see if there is some bootstrap method that might work.

I'm trying to create a usrCandid1 field that will display a list of all non-magical items that are part of the 'Simple' weapon proficiency.

If I use this for my expression, I was expecting to get a list of items that have the NormalWep component, as well as the Simple weapon proficiency.

field[usrCandid1].text = " component.NormalWep & wProfReq.Simple "

If I just use that, the dropdown list will only contain weapons that match those requirements that my character currently has on them.

If I switch the 'restrict First List' drop down to 'All Things', it fills the list up with magical and non magical versions of the Simple Weapon proficiency as well. So, this is getting closer, but I'm not sure why it isn't honoring my NormalWep component.

 

[dungeonguru]

I believe that in many cases, especially staffs, the bootstrapped weapon that is attached to the magic item has to be a "normal" weapon due to timing errors that are generated from magical weapons.

Since a lot of the magic staff "weapons" are actually helper items, you might be able to drop some more off by changing your code to be:

field[usrCandid1].text = "component.NormalWep & wProfReq.Simple & !Helper.Helper"

!Helper.Helper says anything that does not have the Helper.Helper tag.

 

[smokeh]

Perfect, your solution worked great, thanks for your quick reply!

 

[smokeh]

Since i couldn't figure out how to bootstrap the chosen item to the minion, my plan was just to have the player manually add the weapons they chose to the minion. After spending 3 more days deep into the editor, and solving a problem with adding a Swim speed to the minion due to an upgrade, I came up with a solution to adding the weapons. The problem is it seems fairly inelegant, and I'm wondering if there is a smarter way to do this. I have tested this out, and it does work as I describe it.

Basically, I'm pre-bootstrapping every simple weapon (and eventually martial weapons due to another upgrade) to the Minion at the start. I'm then assigning a Condition to the bootstrap that checks for the existence of a custom tag on the minion that I'm setting via the player's choice from the menu. In order to handle the user picking 2 of the same weapon I will need to double all of the weapon bootstraps and add a second level of custom tags and conditions (like Custom.Con_wClub2).

field[usrCandid1].text = " component.NormalWep & wProfReq.Simple & !Helper.Helper "

field[usrCandid2].text = " component.NormalWep & wProfReq.Simple & !Helper.Helper "

if (field[usrChosen1].ischosen <> 0) then

If (field[usrChosen1].chosen.tagis[thingid.wClub] <> 0) Then
perform minion[Familiar].assign[Custom.Con_wClub]
endif
endif

Is there a better way to do this? I don't mind spending the time entering the data, but if there is a smarter path than I would love to try that first!

 

[dungeonguru]

Could you give a better explanation of what you're trying to accomplish? Is this a magically summoned minion or something where you don't want the players to have to touch the minion object at all?

 

[smokeh]

Absolutely! I'm trying to convert this variation on the UA Artificer class that includes a Mechanist specialist. The Mechanist specialist starts with a companion where they choose a Chassis and Build, eventually at level 3 they get this ability:

Combat-Ready Construct
Starting at 3rd level you are able to create weapon components for your construct. Choose 2 simple weapons, the mechanical servant is considered proficient with the chosen weapons. The constuct gains the attack action, and follows the normal rules for wielding weapons and attacking.

These weapons may take a different form than a normal weapon. For example, curved blades may be attached to the wings of a flying construct, enabling it to deal slashing damage like a simitar. Whatever its physical description, you can use the game statistics provided for the weapon in chapter 5 of the Player's Handbook.

Additionally, the construct gains proficiency in all saving throws.

You helped me get the dropdown list filtering properly to restrict to simple weapons, and now when chosen the ability looks like this:



At the time, I figured it was good enough and I would just instruct the player to manually add the weapons onto their Construct and they would have reference on their character sheet. However, as I started adding some Upgrade Components I figured out pre-bootstrapping to the minion, and creating a Custom tag to trigger something from the HERO onto the MINION, since Conditions can only reference their own pick.

It isn't absolutely necessary for the weapons to automatically appear on the minion, I'm having fun trying to problem solve some of these issues and get solutions as well as it being slicker if it automatically adds them.

Adding the proficiency's was fairly straightforward, although there may be a ProfSave.all that I couldn't find. I'm also 'cheating' by just adding all Simple Weapons as proficiency, instead of just the weapons chosen by the player. I was eventually going to try to fix that as well, and just assign 2 weapon proficiency.

if (#levelcount[EPArtific] >= 3) then
perform minion[Familiar].assign[ArmProfGrp.WepSimple]
perform minion[Familiar].assign[ProfSave.svCON]
perform minion[Familiar].assign[ProfSave.svINT]
perform minion[Familiar].assign[ProfSave.svWIS]
perform minion[Familiar].assign[ProfSave.svDEX]
perform minion[Familiar].assign[ProfSave.svCHA]
perform minion[Familiar].assign[ProfSave.svSTR]
endif

I will also need to duplicate this skill as a Construct upgrade that allows the same thing for Martial Weapons.

 

[dungeonguru]

Yep, that's a tough one to imagine tackling.

Have you tried grabbing the WepProf tags from the weapon chosen and pushing only the weapon proficiency to the minion? That way you don't have to grant all simple weapons.

Should be something like (pre-levels/10000) :

perform field[usrChosen1].chosen.pulltags[WepProf.?]
perform minion.pushtags[WepProf.?]

I haven't tested that against a minion, but the code works for hero, so it should work the same.

Also, the all saving throws is svAll so you can drop to a single line

perform minion[Familiar].assign[ProfSave.svAll]

when you write the script with the editor, you can hit the Find Thing... button and type in save or even just sv and it should pick things that have the word save.

One way to try and tackle this would be to create two Helper weapons (they have the Helper.Helper tag to keep them from showing in the normal selection boxes). Don't give those weapons any information other than a name like Built-in Weapon 1 - no damage or anything other than the Simple proficiency. Bootstrap those two weapons to the minion and then step through each of your chosen weapons and copy the damage fields from them into the appropriate bootstrapped weapon.
Something like:

perform field[usrChosen1].chosen.pulltags[?.?]
perform minion.childfound[[COLOR="Red"]BuiltinWeapon1ID[/COLOR]].pushtags[?.?]
minion.childfound[BuiltinWeapon1ID].field[wDieSize].value = field[usrChosen1].chosen.field[wDieSize].value
minion.childfound[BuiltinWeapon1ID].field[wDieCount].value = field[usrChosen1].chosen.field[wDieCount].value
... etc ...

Disclaimer: I have not tested the code so I may have mistyped something.

YOu would replace the BuiltinWeapon1ID with your 1st weapons' ID of course.

 

[smokeh]

Interesting, very interesting. I like the idea of a blank 'helper' weapon that is then overwritten with the appropriate stats. It scales up to simple and martial weapons, and would also allow for additional weapons to be added without modifying the class.

I'm going to play around with all of these options, and I'll update here in case anyone else ends up with a similar question.

 

[smokeh]

I actually remember I tried ProfSave.svAll for assigning all saves, but for whatever reason that tag doesn't get added to the minion when the individual ones work.

The weapon proficiency code works great, it adds the specific weapon proficiency to the minion when it's chosen.

I started looking into implementing the weapons script, but I'm getting an error with trying to pull all the tags from my choice with this: pulltags[?.?]. It doesn't seem to allow you to wildcard the tag group. I'm looking to see if there is another way to copy all of the tags off of a specific pick from the hlkitwiki.

 

[dungeonguru]

Yeah, forgot about that on the pull you have to have the group ID.

Pulling all the tags would be overkill, maybe stick to the tag groups like [wProperty.?], [DamageType.?] and pull/push those. Between that and the base damage fields, it would cover most of what you're trying to do while you tweak it.

 

[smokeh]

Yeah, I looked at manually moving groups, I wasn't too sure what was necessary, but I'll take a look and see if I can get the main tags that I'll need.

While trying to find a different solution, I found another one of your threads helping someone with something similar that lead me down the path of a Configurable. Using a configurable, I was able to get a new tab to pop when the upgrade is added that I possibly could configure to show a list of simple weapons. Of course the tab is showing up on the HERO not the minion, which won't help me add the weapons to the minion. If I wanted to go that route I would need to have the special ability actually added on the Minion I think.

At this point, I'm going to try manually defining some weapon tag groups and see how well that works. If that still gives me issues, I think having the user just manually pick their weapons on the minion isn't really that big of a deal.

 

[smokeh]

In the end, I didn't like how the custom blank weapons would still appear on the Minion until you overwrote them. The Wondrous Invention skill from the UA Artificer that I am copying even has a note in there to make sure you add the item you pick yourself.

I'm just going to include a note saying that you need to manually add your chosen weapons to the Minion directly, and that should be fine for all possible use cases.