Aug 27, 2013, 08:37 AM
Some of us may recall that in RCT2 sometimes when we clicked on a route grid to locate an employee we got an error message "no employees in park yet". Ordinarily this meant the employee who belonged to that route had not yet been placed on the map. At other times it meant we were seeing a "phantom" route grid from a fired employee which was a result of a bug in RCT2.
I understand that the bug has to do with the fact that RCT2 uses a separate "master map" for each type of employee and that this master map is used to display the "locator grid." When a routed employee is fired the master map does not get updated to remove that employee's route, leaving "phantom" grids in the locator display.
Sometimes it helped if one remembered to delete the patrol areas prior to firing any staff but no one could remember to do this every time and when needed there was a work-around that could be used to update the master map.
Every once in a rare while in RCT3 I’ll come across a staff member who is simply standing there a few squares outside his patrol area “lost.†If I pick him up and put him back in his patrol area he’s fine after that. I was wondering if this might be the result of a master map bug in RCT3 that’s similar to the bug which was in RCT2.
I understand that the bug has to do with the fact that RCT2 uses a separate "master map" for each type of employee and that this master map is used to display the "locator grid." When a routed employee is fired the master map does not get updated to remove that employee's route, leaving "phantom" grids in the locator display.
Sometimes it helped if one remembered to delete the patrol areas prior to firing any staff but no one could remember to do this every time and when needed there was a work-around that could be used to update the master map.
Every once in a rare while in RCT3 I’ll come across a staff member who is simply standing there a few squares outside his patrol area “lost.†If I pick him up and put him back in his patrol area he’s fine after that. I was wondering if this might be the result of a master map bug in RCT3 that’s similar to the bug which was in RCT2.