68 replies to this topic

[Fennek]

Regarding Ts25minimod, SCS and especially(?) Detectable Spells: I can confirm what a Japanese guy reported, that the sorcerer of "The sufferings of a sorcerer"-component (which is still in the expert-installation, but the next one I'll translate) behaves a bit strange. He should actually arbitrarily cast (harmless) spells, but doesn't do that if SCSII is installed. It might also be linked with the mage-AI (not DS), don't know it yet, have to test it (what might take until next week, since I might not have internet access until Monday...).

(So the point of time has come that the name of this thread is not right anymore... )

Edited by Fennek, 17 November 2010 - 06:15 AM.

[Hoppy]

Regarding Ts25minimod, SCS and especially(?) Detectable Spells: I can confirm what a Japanese guy reported, that the sorcerer of "The sufferings of a sorcerer"-component (which is still in the expert-installation, but the next one I'll translate) behaves a bit strange. He should actually arbitrarily cast (harmless) spells, but doesn't do that if SCSII is installed. It might also be linked with the mage-AI (not DS), don't know it yet, have to test it (what might take until next week, since I might not have internet access until Monday...).

(So the point of time has come that the name of this thread is not right anymore... )

You might be able to avoid the problem by giving the sorcerer a custom override script for the spells/actions he needs to setup and let his default script be the regular mage AI (like mage18.BCS) or something similar.

What scripts does he have assigned to him with just the TS25 mod and what does he have after SCSII is installed?

[Fennek]

@Hoppy: I did some tests while I was away. The problem is not linked with DS, but simply with SCSII-Smerter Mage AI.

Without SCSII, the Race script is Mage12A.bcs; with SCSII it is DW#2CON6.bcs

(Death, Default, Override and Dialog-Scripts, all special scripts from the mod itself, are not changed.)

So one has - somehow - to prevent SCSII from changing the .cre's Mage12A.bcs... Or maybe somebody knows a better solution...

[Wisp]

So one has - somehow - to prevent SCSII from changing the .cre's Mage12A.bcs... Or maybe somebody knows a better solution...

Give it a custom-named script. SCSII doesn't touch those.

[Fennek]

Thanks. Just to take care that I understood it: I prepare a new script (Ts25blah.bcs or whatever), copy and paste in the text of Mage12A.bcs and assign it to the .cre? (And let the new .cre be put in via the BWP-Fixpack; oder let the Fixpack assign the new script; this part is not that relevant, sonce Leonardo probably knows how to do it).

[Wisp]

Copy the textual script into ts25blah.baf (distributing BCS files is unwise, not to mention annoying) and put it somewhere in the mod folder.

Then, in the TP2, you write:

COMPILE ~path/to/script/ts25blah.baf~
//COPY or COPY_EXISTING your cre file
  WRITE_ASCII /*insert offset here*/ ts25blah #8

Edited by Wisp, 22 November 2010 - 03:09 AM.

[Fennek]

Excellent, thank you! Another component bug-free (I guess...)

[Lollorian]

I prepare a new script (Ts25blah.bcs or whatever), copy and paste in the text of Mage12A.bcs

You can avoid copy-pasting mage12a.bcs by letting WeiDU do your dirty work

Use this code AFTER line 1285 in the non-BWPFixpacked ts25mini.tp2

COPY_EXISTING ~Mage12A.bcs~ ~override/Ts25blah.bcs~

COPY_EXISTING ~tz25_#ma.cre~ ~override~
  PATCH_IF SOURCE_SIZE > 0x2d3 BEGIN
    WRITE_ASCII 0x258 ~Ts25blah~ #8 //Race script
  END
BUT_ONLY_IF_IT_CHANGES

Dunno if the first COPY_EXISTING needs a BUT_ONLY_IF_IT_CHANGES though

[Miloch]

Dunno if the first COPY_EXISTING needs a BUT_ONLY_IF_IT_CHANGES though

No, because you're not changing it, so quite possibly it wouldn't copy it (not even to a new resource) with the BUT_ONLY.