rex travels to megaton if not immediately hired

[yarrmateys]

while i was at the kings and got rex available, i had ed-e with me, so i couldn't take rex with me immediately (the message about having that slot occupied already). i decided to get back for him later, only to find he wasn't anywhere at the kings, but all the way in dc, inside megaton. i think the problem here is that if he's not immediately hired no proper variables are set (esp. bRexFiredWasteland, which remains at 0, making the game think he was fired in dc), so he (and possibly some others) meet the conditions required for the capital wasteland package to activate, prompting them to go over there. it may need to check if the companion was actually fired (RexFired to 1) in the ttw fired packages.

edit: same happened to ed-e and veronica after completing lonesome road. after they got auto-dismissed at the start of the dlc they ended up in megaton. maybe changing it for nv followers so that the FiredWasteland variable is 0 for mojave and 1 for capital wasteland would help solve any other possible problems with this. though this may affect the fo3 dlc auto dismissals too, sending them all the way to mojave.

edit2: oh i see. TTWFNFireAllFollowers doesn't set the *FiredWasteland variable when it sends all of the characters to their respective wasteland's locations, it's always set to 0, making the game assume it was done in capital wasteland. so even after ex. ed-e is sent to primm, his primm package won't be active due to bEDEFiredWasteland being at 0, but the megaton one will, so he'll just travel to megaton right afterwards.