Effective use of MakeGlobal()

[Aegnor]

Ok, so I'm working on a familiar mod. Well all of a sudden nothing would work, the summoned familiar wasn't made global. It would not follow through areas.

Later figured out that this was because of me changing the death variables, and that MakeGlobal() and MoveGlobalObject() both targets the death variable and not the cre name.

A couple of minutes later, I figured out a use for this. Since I changed ALL the familiars death variables, I could from there both make global and move the familiar in two script blocks, no matter what sort of familiar I summoned.

Example:

// After I make weidu patch all the familiars' death variables, and have summoned one of the familiars.

IF
  Global("DKDMakeGlobal","GLOBAL",1)
THEN
    RESPONSE #100
             SetGlobal("DKDMakeGlobal","GLOBAL",2)
             ActionOverride("familiar",MakeGlobal())
END

IF
       !Dead("famdust")
       !Global("DKDFamStayHere","GLOBAL",1)
       !Global("DKDFamInPack","GLOBAL",1)
       !InMyArea("familiar")
THEN
    RESPONSE #100
        MoveGlobalObject("familiar",Player1)
END

[Ghreyfain]

Huh, I checked my IDS and it doesn't even have MakeGlobalObject() in it.  But yeah, unless you're creating the creature, it's the script name/death variable that gets checked for things like that.

[SimDing0™]

MoveGlobalObject, Ghrey.

[Ghreyfain]

Oh.

Shit.

I, uh... just woke up.

[Andyr]

I use a similar method to the first poster in the Elai mod, though I have a Range check rather than an InMyArea check for other reasons.