Member
Join Date: Sep 2008
Posts: 48
|
Here's another one...
I am adding a weapon property called Quick Loading which can only be applied to corssbows. It gives the weapon access to an extradimensional space that can hold up to 100 bolts. I would like to make it so that when this porperty is added to the weapon, the weapon would then show up as a container, like a bag or pack, to which the bolts could be added. I have tried the following in an eval script on the item property set to First, 10000: var result as number result = parent.assign[thing.holder] but it doesn't seem to have any effect. I have, in my desperation, even tried bootstrapping the Bag of Holding... :roll: Any advice? |
#1 |
Member
Join Date: Sep 2008
Posts: 48
|
Anyone? Anyone? Beuller? Anyone?
|
#2 |
Senior Member
Lone Wolf Staff
Join Date: Dec 2008
Posts: 4,690
|
Dastir wrote:
> > > Here's another one... Smile > > I am adding a weapon property called Quick Loading which can only be > applied to corssbows. It gives the weapon access to an extradimensional > space that can hold up to 100 bolts. I would like to make it so that > when this porperty is added to the weapon, the weapon would then show up > as a container, like a bag or pack, to which the bolts could be added. > > I have tried the following in an eval script on the item property set to > First, 10000: > > var result as number > result = parent.assign[thing.holder] > > but it doesn't seem to have any effect. I have, in my desperation, even > tried bootstrapping the Bag of Holding... Rolling Eyes Sorry for the delay in response - I was checking up on how things worked so I could provide a more helpful answer than "Sorry, that won't work" (which you've already discovered). The "thing.holder" tag is only obeyed when it's assigned directly to a thing, not through an assign statement. (This is because "holder" things require extra storage to be allocated for them, which only happens the first time they're created.) I don't think you can do this right now, but I think I can figure out a way to make it work in the next version of Hero Lab (which should be out soon). I'll keep you updated. -- Colen McAlister, colen@wolflair.com |
#3 |
Member
Join Date: Sep 2008
Posts: 48
|
Thanks Colen!
I must say I am really quite happy with how helpful you and Rob are. You have a fantastic product that has quite a learning curve associated with it, and you are very patient in answering all the myriad question that I, and users like me, throw your way. Keep up the great work! |
#4 |
Senior Member
Lone Wolf Staff
Join Date: Dec 2008
Posts: 4,690
|
Dastir wrote:
> > > Thanks Colen! > > I must say I am really quite happy with how helpful you and Rob are. You > have a fantastic product that has quite a learning curve associated with > it, and you are very patient in answering all the myriad question that > I, and users like me, throw your way. > > Keep up the great work! Hi Dastir, Rob and I have just discussed a way to allow you to do what you want, but unfortunately we're not quite ready to include it in the data files yet. Before the authoring kit releases, we need to do a final sanity check of a few features in Hero Lab, including this one, to make sure we're not exposing any nasty problems that will come back to bite us in the future. Otherwise, we're potentially opening up a can of worms for ourselves in a few months when it someone starts using a feature in a way we didn't intend, and it begins misbehaving as a result. Until we finalize the details on this, I can suggest a temporary solution - add a "Custom Container" to the hero on the Gear tab, and set the name to something like "Magical Bolt Storage". Now you can store the relevant items in this container, and move them all at once to the new magical container once it's available. Hope this helps, -- Colen McAlister, colen@wolflair.com |
#5 |
Member
Join Date: Sep 2008
Posts: 48
|
Good suggestion, I will do that.
Thanks again! |
#6 |
|
|