Scar

Hiya,

I got the same problem here on OS X. Will this be fixed in future WeiDU?

Armin

You can also use WeiDU for decompiling scripts. Simply type "weidu scriptname.bcs" within your BG dir, and you'll get a readable scriptname.baf in there.

Thanks, it worked out allright - weidu-mac 155 up and running.

- More than once I ?lost? a 10th level spell when I clicked on the ability in the middle of combat but then had to click on another party member.  When I clicked back on the PC after the HLA was ?used? the menu was not visible.

Ah, yes, that can be an annoyance, but I thought that's a known fact to power gamers who tried each class and kit at least once .

At the present, there's three spells suffering from that, Spell Immunity, Magic Weapon and Nahal's Reckless Dweomer. It's most annoying when playing a Wild Mage (especially a chaotic one, who tends get reckless in battles ), so I adopted a play style that involves the space bar as material component of any spell. IMHO, if you know the limitations, they are easily overcome - with a bit of discipline, of course.

Anyway, if someone wants to playtest the suggested TD mechanics, a Wild Mage using NRD quite frequently does come close...

My main thought after seeing this ?in play? was that I would have like a pop-up menu similar to what the spell triggers and contingency type spells use.

I think that would be A. more difficult to code and B. impractical, since quite often you need to aim your spell at something, which is not possible with the menu blocking your view.

...this seems the core problem for me to use it. 

That's easy (tho not tested, due to the lack of WeiDU v155):

SET "col" = 0
SET "cap" = ~dummy~
WHILE NOT ("%cap%" = ~RANGER~) BEGIN
  SET "col" = ("%col%" + 1)
  READ_2DA_ENTRY 0 "%col%" 3 "cap"
END

As soon as it reads RANGER from the table's titles, the loop exits and "col" holds the coordinate you need. Well, some error handling would be neccessary in case RANGER is not in the table.

The real question is, what would happen if above loop would run out of the boundaries of the table and read an 'empty' value? If it'd be a defined value for end-of-line, you could check for that and use the loop to determine a table's dimensions as well as error handling.

EDIT: Damnit, I knew there had to be a catch... I thougth I did something like this

WHILE NOT ("%cap%" = ~RANGER~) BEGIN

before, but apperantly I didn't. I was just toying around, and it seems to me that WeiDU can't compare a variable (filled with READ_ASCII) with a string. It chokes with:

ERROR: [ar0907.are] -> [override] Patching Failed (COPY) (Failure("int_of_string"))

Here's the code I played with, if someone else wants to try:

COPY_EXISTING ~ar0907.are~ ~override~
    READ_LONG 0x5C "infooffset"     // Where to find info points?
    READ_SHORT 0x5A "infocount"     // How many info points are there?
    WHILE "%infocount%" BEGIN
        SET "infocount" = ("%infocount%" - 1)
        READ_ASCII ("%infooffset%" + "%infocount%" * 0xC4) "infoname"   // What's this point called?
        WHILE ("%infoname%" = ~Trigger Point 3~) BEGIN
            WRITE_SHORT ("%infooffset%" + "%infocount%" * 0xC4 + 0x20) 2
        END
    END