Atoms

Vars | |
created_atoms | initAtom() adds the atom its creating to this list iff InitializeAtoms() has been given a list to populate as an argument |
---|---|
initialized_changed | A count of how many initalize changes we've made. We want to prevent old_initialize being overridden by some other value, breaking init code |
Procs | |
CreateAtoms | Actually creates the list of atoms. Exists soley so a runtime in the creation logic doesn't cause initalized to totally break |
InitAtom | Init this specific atom |
InitializeLateLoaders | Processes all late_loaders, checking the length each iteration and prevents duplicate calls This is necessary because of an edge case where there might be simultanious calls to InitializeAtoms |
fix_atoms_locs | Force reset atoms loc, as map expansion can botch turf contents for multitiles This is obviously a bandaid fix, see CM MR !2797, /tg/ PR #65638, and the BYOND Bug Report: http://www.byond.com/forum/post/2777527 |
initializing_something | Returns TRUE if anything is currently being initialized |
set_tracked_initalized | Use this to set initialized to prevent error states where old_initialized is overridden. It keeps happening and it's cheesing me off |
Var Details
created_atoms

initAtom() adds the atom its creating to this list iff InitializeAtoms() has been given a list to populate as an argument
initialized_changed

A count of how many initalize changes we've made. We want to prevent old_initialize being overridden by some other value, breaking init code
Proc Details
CreateAtoms
Actually creates the list of atoms. Exists soley so a runtime in the creation logic doesn't cause initalized to totally break
InitAtom
Init this specific atom
InitializeLateLoaders
Processes all late_loaders, checking the length each iteration and prevents duplicate calls This is necessary because of an edge case where there might be simultanious calls to InitializeAtoms
fix_atoms_locs
Force reset atoms loc, as map expansion can botch turf contents for multitiles This is obviously a bandaid fix, see CM MR !2797, /tg/ PR #65638, and the BYOND Bug Report: http://www.byond.com/forum/post/2777527
initializing_something
Returns TRUE if anything is currently being initialized
set_tracked_initalized
Use this to set initialized to prevent error states where old_initialized is overridden. It keeps happening and it's cheesing me off