MUD Coding

03-24-2003, 01:30 AM

Got a way to make it so immortals don't suffer from lag?

KaVir · 03-24-2003, 04:23 AM

Make them all live together in the same house as the server.

enigma@zebedee · 03-24-2003, 07:37 AM

Get them all broadband, get a decent connection for the server.

It works for me ;-)

More seriously lag is a product of:
1: Slow connection from server to internet
2: Slow connection from user to internet
3: Overloaded servers
4: The internet

Unfortunately only points 1&3 are under your control, 2 is in the hands of the user and 4 is down to the whims of the internet.

On a brighter note we have sorted out what we can and its very rare that 4 is a problem - I am on broadband and if my commands don't respond instantly then I consider it laggy...

03-24-2003, 08:33 AM

What I meant is anyone got the way to make it so imms don't suffer from lag from spells. like waiting three seconds due to pulses and such. Like casting create spring makes you lag a few seconds till you can do another move. That is what I meant

Xerihae · 03-24-2003, 08:56 AM

(Sorry, enigma is right. This explanation is based on my knowledge of ROM 2.4b6, and may or may not be relevant to other codebases.)

For spells, look in do_cast (usually in magic.c, this is all off the top of my head, I'm at college so dont have any access to code) and find the line:

WAIT_STATE (ch, skill_table[sn].beats, TRUE); (or something like that, find the WAIT_STATE anyway)

Add above it:

if (!IS_IMMORTAL(ch))

This will only give the casting lag to mortals. For skills, you'll probably have to go through them all and add that line above all the WAIT/DAZE states.

That ought to do it. I've done it for my own MUD, so I'll check when I get home and let you know if I got anything wrong. That is of course assuming some other more knowledgeable person in the MUD'ding community doesn't correct me before then

enigma@zebedee · 03-24-2003, 11:46 AM

Yeeh, that is an entirely mudlib dependant question!

Without knowing what sort of driver/mudlib etc you are using then we can't do any more than guess.

Find the section of code which causes the mortals to wait and make it conditional on whether you are an Imm or not.

Personally I don't like the idea of locking people up like that though - the way we do it is that spells can take any amount of time to cast and don't block commands, but certain commands (like casting another spell or moving) will abort the spell.

Immortal Lag - Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
A Good Immortal	Sanvean	MUD Administration	6	08-02-2012 09:51 PM
Immortal MUSH	Rhiva	Advertising for Players	0	12-28-2005 12:29 AM
Immortal University	Ntanel	MUD Announcements	0	11-11-2004 10:33 PM
If you need a immortal/mod/builder im here!	Azhag	Advertising for Staff	1	10-11-2004 12:49 PM
Immortal University	DarrylTheHitman	MUD Announcements	5	01-31-2004 10:17 PM

03-24-2003, 01:30 AM	#1
Verboden Faction Posts: n/a	Got a way to make it so immortals don't suffer from lag?

03-24-2003, 04:23 AM	#2
KaVir Legend Join Date: Apr 2002 Name: Richard Home MUD: God Wars II Posts: 2,010	Make them all live together in the same house as the server.

03-24-2003, 07:37 AM	#3
enigma@zebedee Member Join Date: Mar 2003 Posts: 70	Get them all broadband, get a decent connection for the server. It works for me ;-) More seriously lag is a product of: 1: Slow connection from server to internet 2: Slow connection from user to internet 3: Overloaded servers 4: The internet Unfortunately only points 1&3 are under your control, 2 is in the hands of the user and 4 is down to the whims of the internet. On a brighter note we have sorted out what we can and its very rare that 4 is a problem - I am on broadband and if my commands don't respond instantly then I consider it laggy...

03-24-2003, 08:33 AM	#4
Verboden Faction Posts: n/a	What I meant is anyone got the way to make it so imms don't suffer from lag from spells. like waiting three seconds due to pulses and such. Like casting create spring makes you lag a few seconds till you can do another move. That is what I meant

03-24-2003, 08:56 AM	#5
Xerihae Senior Member Join Date: Oct 2002 Name: Chris Location: Wolverhampton, UK Posts: 357	(Sorry, enigma is right. This explanation is based on my knowledge of ROM 2.4b6, and may or may not be relevant to other codebases.) For spells, look in do_cast (usually in magic.c, this is all off the top of my head, I'm at college so dont have any access to code) and find the line: WAIT_STATE (ch, skill_table[sn].beats, TRUE); (or something like that, find the WAIT_STATE anyway) Add above it: if (!IS_IMMORTAL(ch)) This will only give the casting lag to mortals. For skills, you'll probably have to go through them all and add that line above all the WAIT/DAZE states. That ought to do it. I've done it for my own MUD, so I'll check when I get home and let you know if I got anything wrong. That is of course assuming some other more knowledgeable person in the MUD'ding community doesn't correct me before then

03-24-2003, 11:46 AM	#6
enigma@zebedee Member Join Date: Mar 2003 Posts: 70	Yeeh, that is an entirely mudlib dependant question! Without knowing what sort of driver/mudlib etc you are using then we can't do any more than guess. Find the section of code which causes the mortals to wait and make it conditional on whether you are an Imm or not. Personally I don't like the idea of locking people up like that though - the way we do it is that spells can take any amount of time to cast and don't block commands, but certain commands (like casting another spell or moving) will abort the spell.

MUD Coding

Immortal Lag