|
|
Post by CrunchX on May 26, 2004 15:37:56 GMT
I've just been on the server and it crashed twice in about 30 minutes, before each crash I was seeing a lot of script errors that I hadn't seen before (not ATS errors heheh). I forget exactly what the error was but it said something about ent_area and wsblack  |
|
|
|
Post by Makzimia on May 26, 2004 16:22:24 GMT
TMI is NOT a critical error, it means something is working overtime, and has NO effect on the server, normally, that one is because of a player entering and leaving having their magic spells depleted.
I will however mention this to addicted, it SHOULDN'T make a difference though...
|
|
|
|
Post by addicted2rpg on May 26, 2004 16:50:37 GMT
*groan*
I don't want to do that delay nuts! That is just plain wrong. TMI is just plain wrong. It was meant to catch infinite loops so coders can't run a module right into the ground by having a script going forever. But the fact of the matter is, we just have a lot of instructions. They arn't looping forever. All those scripts have logical termination. Bioware has given us a data set that is too large. From Aaganazzar's scorcher all the way to Wounding Whispers, there is just a lot of spells and that is the only functionality available to remove them. I can't help it if some sorcerers can have hundreds of castings over the course of their magic. They should give us less spells or let our scripts run more instructions before terminating them as infinite. I can understand the error. What I can't understand is why the max instruction count wasn't increased in 1.29, let alone 1.62
Bloody Bioware! gaaarrrgghhh!
|
|
