Senior Member
Volunteer Data File Contributor
Join Date: Mar 2007
Posts: 1,245
|
So I notice that these have Eval Scripts (around Final 15000) like this:
call CalcValue ~ Use our value field as the speed at which we can swim field[livename].text = field[name].text & " (" & field[Value].value & " feet)" I think I just figured something out! The "call CalcValue" must look at the Value.? tag applied to the thing and then translate it into a number for the Value field, am I right? I am writing a script that adds to Burrow speed if it is already present on the hero. Like so: ~ Add to our Burrow speed (if any). if (hero.childfound[xBurrow].field[Value].value <> 0) then hero.childfound[xBurrow].field[Value].value += 10 endif Unfortunately, the way burrow is written right now there is an issue with the timing. Since most races bootstrap xBurrow with a tag, they do not have a value in their Value field until they are named. If I run my script before Final 15000, then the tag is not yet converted, a 0 is read, and no addition happens. If I run it on or after Final 15000 the value does change, but the name has already been set so the user can't see it. Mathias, can you maybe separate the CalcValue and the part where the script is named by a bit so something can happen in between? |
#1 |
Senior Member
Volunteer Data File Contributor
Join Date: Mar 2007
Posts: 1,245
|
Upon further review, it looks like only xBurrow, xFly and rDarkvision are suffering from this problem. Other ones like xClimb and xSwim have been separated already.
|
#2 |
Senior Member
Volunteer Data File Contributor
Join Date: Mar 2007
Posts: 1,245
|
Also see the note I made in the bugs thread, about old races' Burrow speeds not working.
|
#3 |
|
|