Converting EE Mods to EET

[Endarire]

Greetings, all!

Let's assume I have an EE-compatible mod I want to be made EET compatible.  When is running the automatic converter enough?  How do I know if it failed, it succeeded, and in what ways?  What else should I know about this at present?

Thankee!

[jastey]

I have no experience with the automatic converter.

This is what I wrote in a hidden forum before with regard to making old BGII (NPC) mods EET compatible. For BG1 mods it depends whether it already covers the "Crossing the Great Divide" (back in the day between BGT and Tutu, but the principle is the same between BG:EE and EET) or not.

Quote

My Ajantis BGII mod is an example for BGII mod with own SoA -> ToB transition (meaning it does not use the Adding support for NPC transition system function provided by EET. I'm not sure it's a good example, though, as it also has to consider the BG1 Ajantis with the according fate spirit entries EET contains, etc.

The short, quick and dirty way to make a BGII:EE NPC EET compatible is the following:

The EET Contiuous Chapter System you'll need always. Changes for this: the addition to the tp2 ALWAYS block, changing the chapter numbers to the according OUTER_SPRINTs %bg2_chapter_x% and adding the EVALUATE_BUFFER to the compilation commands of the relevant files in the tp2.

Then there are two ways to proceed from here for the ToB transition (for a BGII-only NPC).

1. Using the EET_NPC_TRANSITION function AND disabling the following for EET:
   1. summoning via fate spirit dialogue (FATESP.dlg)
   2. the disabling of the possibility to summon via fate spirit if NPC is in party upon soA-ToB transition (usually done by setting the variable in AR4000.bcs)
   3. creation of NPC if called via fate spirit (AR4500.bcs)
2. Not using the EET_NPC_TRANSITION function. In this case, the summoning of the NPC has to be added to FATESP.dlg, the possibility to do so has to be disabled if the NPC is in party upon SoA->ToB transition, and the creation of the NPC in AR4500.are has to be provided by patching AR4500.bcs. In addition to this (and this is new), the change of the override script from the SoA to the ToB one has to be done by hand in AR4000.bcs if the NPC is in party, as it will not be done automatically.

Apart from that, for a BGII NPC you should be fine. Care has to be taken if the mod was developped on BGT with all the BG1 ressources, as EET uses own filenames for the BG1 files that share names with BGII files, but that shouldn't be an issue for most BGII mods.

Theoretically, EET provides much more possibilities for the continuous NPC summoning in ToB etc. It does, for example, distinguish between "NPC was in party", "NPC was never in party" (-> will not be available for summoning in a continuous game), and "is dead" (-> summoning is available but NPC will not spawn, obviously).

For the "old" BGII NPC, the continuous system is a bit dangerous, though, as it will move the BGII NPC to ToB as (s)he was left in SoA - in case that was in chapter two, the NPC will be level 7/8/9 and the player might be a bit piqued if there is no script added to boost the XP a little.

Addition to that: PIDs need to include "IsGabber(Player1)" into the trigger, then EET automatically adds triggers to the SoA part so it doesn't block the ToB dialogues.

[Endarire]

@jastey
Thankee!