1
2
Oct 3 2015, 3:59 pm
|
|
Progress. This is with no map at all.
|
These are all listing I have for those..
atom var/tmp/list/hitlist var/circlecooldownlist var/tmp/Name[2] var/tmp/Name2[2] var/tmp/NameOutline[2] I have no listing variables for datums or turfs |
atom Bingo. You really only want those defined on things that actually have names, cooldowns, or whatever hitlist does. This is a classic case of embedding behavior too low in the hierarchy. $5 all of these things should be embedded in /mob. |
In response to Ter13
|
|
Ter13 wrote:
$5 all of these things should be embedded in /mob. $10 for /atom/movable |
In response to Ter13
|
|
Ter13 wrote:
atom This, and you should probably be initializing those lists when you're ready to use them. |
is there a way you can initialize an array like that in realtime or is it not possible? Name=new(2)?
|
Question: What's the name array for? It's probably better to chase down a better implementation than try to find workarounds.
|
You can always do something like:
var/L[] Probably. Or look for a better way. |
In response to Super Saiyan X
|
|
Fat Albert got it right, it's new /list (2), where /list can be left out of the variable is a list type.
|
yeah thx guys. I got it. I still would like for you to look at something tomorrow if you still got time. And thank Kaiochao on that information about listing earlier I did some heavy revisions on my source about that bad listing habit of mine. I'll let you know if it seems to have improved anything.
|
1
2