![]() |
Member
Join Date: Jul 2015
Location: Ottawa
Posts: 58
|
nope, I understand your question better now. Here's some:
- Boots of Elvenkind - Cloak of Elvenkind - Bracers of Archery, Lesser - Cloak of Resistance (+1) - Bracers of Armour (both +1 and +2) - Amulet of Natural Armour - Ioun Stone, Dusty Rose Lastly, and I dont know if this is even possible, can an item with charges (wands) be rendered... unselected? Unlisted? Likely not, but if you have a bright idea, I'll make local copies, cause there's just too many of them. And then, I've got one legacy weapon that isn't responding. I want to do some further testing tomorrow before I ask for more help though. The others have reacted properly, but this one isn't having its various Specials disapper from the list, and its STR bonus is sticking around too. Very strange. |
![]() |
![]() |
Senior Member
Join Date: Mar 2013
Location: Melbourne, Australia
Posts: 1,059
|
Even AD&D by TSR used the spelling "glamer". (I can't be bothered checking earlier versions.) A quick search notes that the spelling is an archaic form, but certainly legitimate. I'd prefer it to be 'glamour', just like I'd like to see 'armour', but that ain't happening.
Current RPG's: Pathfinder (GM), Pathfinder (Player), Gamma World (GM, Pathfinder homebrew). HeroLab: 3.5 & Pathfinder. HL User Files for PF: Greyhawk Setting, Gamma World (WIP). DM and player of D&D since 1980. |
![]() |
![]() |
Senior Member
Join Date: Jul 2010
Posts: 3,126
|
Quote:
As for "armour", pffftt. |
|
![]() |
![]() |
Senior Member
Join Date: Jul 2010
Posts: 3,126
|
Quote:
Quote:
Timing: final/10000 Code:
doneif (field[pIsOn].value = 0) foreach pick in hero from BaseMagicI where "Helper.ShowCharge" perform eachpick.delete[Helper.ShowCharge] nexteach Quote:
![]() If you're talking about specials bootstrapped to the item, the script isn't set up to disable those. I'm not sure the best approach. Would be nice just to add a script to the adjustment to handle it, but that would require those specials having some tag that can identify them as magical. Barring that, we could assign the User.Disabled tag to the hero at First/450 with an adjustment to the second script then use a bootstrap condition at First/500 of "!User.Disabled" on the bootstraps for the item. Last edited by Sendric; March 16th, 2023 at 04:23 AM. |
|||
![]() |
![]() |
![]() |
Thread Tools | |
Display Modes | |
|
|