A list of the current amounts for limited global data in the game, such as datums/lists/internal arrays/strings/mob/obj/image/etc. For example "Mob: 42/65535"
This list could be displayed in the Profile World page. The information basically allowing developers to notice a build up or leaks; rather than waiting until an error is produced for reaching the limit. Some of these issues can be difficult or impossible to track down late in development.
"Internal Arrays" should definitely be on the list, there's little information about them except they might have something to do with overlays(and probably input/alert prompts). Regardless, several developers have had issues with them with no resolution.
I'm aware there are ways for the developer to track several of these. Overriding New/Del will work fine for atoms. Looping over the world contents for variables of the type "/list" is also possible. Even using /ref with incrementing addresses can be used to count unique strings in the game among a few other things.
Even so, it doesn't seem like something that developers should need to make hacky workarounds to find.
ID:133795
 Dec 26 2007, 1:57 pm
|
|
|
Dec 27 2007, 1:47 pm
|
|
Masterdan
 |
fully supported.
|
A potentially more useful way to provide this information could be in a read-only variable.
This could allow developers to automatically check them and reboot the game if a limitation is too close to being breached(Generally some games become useless if they can't create new objects, for example). Also allowing the developer to output debug statements before/during/after systems under suspicion. Prevention is definitely the better option for developers but it's not impossible to overlook something. | |