MUD Coding

Torren · 04-22-2002, 08:23 AM

Ok let me know if this has happened to you. I'm having some sort of memory error where a mob dies but it doesn't get removed from the char_list, haven't messed with extract_char. Also I've had occurances where the mobs have ignored pieces of code. Like sleeping mobs wondering when in the code it says if the position is less then fighting continue. and then the wander code starts. Any ideas?

Koryon · 04-23-2002, 11:08 AM

1) Get Rational Purify, but that's probably not an option...

2) Check things you've changed lately?

3) You DID do a clean compile, right? (rm *.o; make)

4) If all else fails, open up gdb and step through the process of killing a mob and see what happens

Torren · 04-23-2002, 12:33 PM

Well the problem is it's not always happening I think the mobs not going away is a symptom of a larger problem. I can have it not happen for days or I can have it happen right after the mud reboots. Pain to trace. You check the GDB and it has the mob going through the update_violence check even though it has negative hp and pos_dead. so its by passing all of those checks. its really odd.

Koryon · 04-23-2002, 03:36 PM

Try doing a code search to see everything that changes position, see if something could be changing it to dead without extract'ing the mob, perhaps a mobprog or some such.

Xanferious · 04-23-2002, 08:24 PM

if everything keeps failing, get a gun, load it and shoot the computer...that will teach it to fail...

Koryon · 04-24-2002, 07:21 AM

Torren · 04-24-2002, 08:14 AM

funkalicious · 04-24-2002, 10:49 AM

Im sure that if you shoot your computer, it will fail up the yin yang.

visko · 05-08-2002, 08:58 PM

One of the earlier posts was asking about code changes you have made around the time this bug started popping up. In my (limited) experience, simple code changes with very subtle problems, like writing a check wrong or passing odd data that causes the computer to hiccough, metaphorically speaking, can cause crash bugs that are more annoying and harder to find than anything else in the world.

So...Have you done any code changes that could have affected mobs being taken out of the game/properly killed? It's a pretty easy thing to do, with almost any code change related to fighting and affects.

-Visko

Rom 2.4 Mob errors - Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Errors crashing compile	Sevoric	MUD Coding	24	04-28-2002 12:37 PM
Circle - Death Gate make errors	Eagleon	MUD Coding	11	04-20-2002 10:43 AM

04-22-2002, 08:23 AM	#1
Torren New Member Join Date: Apr 2002 Posts: 28	Ok let me know if this has happened to you. I'm having some sort of memory error where a mob dies but it doesn't get removed from the char_list, haven't messed with extract_char. Also I've had occurances where the mobs have ignored pieces of code. Like sleeping mobs wondering when in the code it says if the position is less then fighting continue. and then the wander code starts. Any ideas?

04-23-2002, 11:08 AM	#2
Koryon Member Join Date: Apr 2002 Location: Canada Posts: 50	1) Get Rational Purify, but that's probably not an option... 2) Check things you've changed lately? 3) You DID do a clean compile, right? (rm *.o; make) 4) If all else fails, open up gdb and step through the process of killing a mob and see what happens

04-23-2002, 12:33 PM	#3
Torren New Member Join Date: Apr 2002 Posts: 28	Well the problem is it's not always happening I think the mobs not going away is a symptom of a larger problem. I can have it not happen for days or I can have it happen right after the mud reboots. Pain to trace. You check the GDB and it has the mob going through the update_violence check even though it has negative hp and pos_dead. so its by passing all of those checks. its really odd.

04-23-2002, 03:36 PM	#4
Koryon Member Join Date: Apr 2002 Location: Canada Posts: 50	Try doing a code search to see everything that changes position, see if something could be changing it to dead without extract'ing the mob, perhaps a mobprog or some such.

04-23-2002, 08:24 PM	#5
Xanferious Senior Member Join Date: Apr 2002 Location: The Void Posts: 490	if everything keeps failing, get a gun, load it and shoot the computer...that will teach it to fail...

04-24-2002, 07:21 AM	#6
Koryon Member Join Date: Apr 2002 Location: Canada Posts: 50

04-24-2002, 08:14 AM	#7
Torren New Member Join Date: Apr 2002 Posts: 28

04-24-2002, 10:49 AM	#8
funkalicious Member Join Date: Apr 2002 Location: US of A Posts: 38	Im sure that if you shoot your computer, it will fail up the yin yang.

05-08-2002, 08:58 PM	#9
visko Member Join Date: May 2002 Posts: 98	One of the earlier posts was asking about code changes you have made around the time this bug started popping up. In my (limited) experience, simple code changes with very subtle problems, like writing a check wrong or passing odd data that causes the computer to hiccough, metaphorically speaking, can cause crash bugs that are more annoying and harder to find than anything else in the world. So...Have you done any code changes that could have affected mobs being taken out of the game/properly killed? It's a pretty easy thing to do, with almost any code change related to fighting and affects. -Visko

MUD Coding

Rom 2.4 Mob errors