Jul 17 2005, 10:21 am
In response to Vito Stolidus
|
|
Ol' Yeller
 |
I don't see you using braces & semicolons. :/
|
I had to kill that habit early, that can actually cause errors.
--Vito NOTE: at the end of a real long line of code, I am actually known to hit ";" before hitting enter to do another line, but I catch myself quick | |
With the while() loop you had earlier, it could generate such a lag which it would make the Dream Seeker "Not Respond". Having who knows how many mobs take a step, search for mobs in view, attack. Stuff like that can pile up quickly.
Some things I have noticed causing Dream Seeker to temporarily or permanently become "Non Responsive" are: Doing WAY too many things in New() procs, especially for things such as NPCs or objects, etc, which are mass produced on startup. Creating way too many objects at once. Giving atoms an icon overlay on startup. There are tons more. ~Jack | |