EQEmulator Forums - Best practice to initialize qglobals?

EQEmulator Forums (https://www.eqemulator.org/forums/index.php)

- Quests::Q&A (https://www.eqemulator.org/forums/forumdisplay.php?f=599)

- - Best practice to initialize qglobals? (https://www.eqemulator.org/forums/showthread.php?t=34572)

Best practice to initialize qglobals?

Here's one way to initialize a qglobal:

Code:

sub EVENT_SPAWN {

        quest::set_proximity($x - 50, $x + 50, $y - 50, $y + 50);

}



sub EVENT_ENTER {

        if(!defined $qglobals{some_nice_qglobal}) {

                quest::setglobal("some_nice_qglobal", 0, 5, "F");

        }

}

Does setting a proximity utilize more resources? than say just checking for the qglobal whether the PC initiates with the NPC by saying something or giving an item, like so:

Code:

sub EVENT_SAY {

        if(!defined $qglobals{some_nice_qglobal}) {

                quest::setglobal("some_nice_qglobal", 0, 5, "F");

        }



        # ...other EVENT_SAY code...

}



sub EVENT_ITEM {

        if(!defined $qglobals{some_nice_qglobal}) {

                quest::setglobal("some_nice_qglobal", 0, 5, "F");

        }



        # ...other EVENT_ITEM code...

}

...or is there another better way altogether?

Or does it even matter?

IMO, the latter is probably better for one small reason: proximity updates only happen at certain intervals and only if the client doesn't already occupy space inside the area. If those don't matter to you then there isn't much of a difference.