Login
User Name:

Password:



Register
Forgot your password?
Vote for Us!
parse description bug
Dec 15, 2017, 10:08 pm
By Remcon
Couple bugs
Dec 12, 2017, 5:42 pm
By Remcon
Bug in disarm( )
Nov 12, 2017, 6:54 pm
By GatewaySysop
Bug in will_fall( )
Oct 23, 2017, 1:35 am
By GatewaySysop
Bug in do_zap( ), do_brandish( )
Oct 18, 2017, 1:52 pm
By GatewaySysop
LOP 1.45
Author: Remcon
Submitted by: Remcon
LOP Heroes Edition
Author: Vladaar
Submitted by: Vladaar
Heroes sound extras
Author: Vladaar
Submitted by: Vladaar
6Dragons 4.3
Author: Vladaar
Submitted by: Vladaar
Memwatch
Author: Johan Lindh
Submitted by: Vladaar
Users Online
CommonCrawl, Sogou, Google

Members: 0
Guests: 1
Stats
Files
Topics
Posts
Members
Newest Member
477
3,706
19,240
608
LAntorcha
Today's Birthdays
There are no member birthdays today.
Related Links
» SmaugMuds.org » Codebases » AFKMud Support & Development » re-connect lag for mortal pla...
Forum Rules | Mark all | Recent Posts

re-connect lag for mortal players
< Newer Topic :: Older Topic >

Pages:<< prev 1 next >>
Post is unread #1 May 12, 2011, 8:07 pm
Go to the top of the page
Go to the bottom of the page

crone
Fledgling
GroupMembers
Posts15
JoinedMay 10, 2011

I use to add some lag for who is not IMMORTAL.
This is because some players to avoid the lag by spells (such as sanctuary) or skills lag, normally reconnect.

I think i've found the solution

in descriptor.cpp
in short descriptor_data::check_playing( const string & name, bool kick )
after
         connected = cstate;
         check_auth_state( ch ); /* Link dead support -- Rantic */
         show_status( ch );
i added
	 if (ch->level < LEVEL_IMMORTAL)	/* lag for mortals on reconnect C */
	 {	
		  ch->WAIT_STATE( 50 );
	 }

and in short descriptor_data::check_reconnect( const string & name, bool fConn )
after

        connected = CON_PLAYING;
        check_auth_state( ch ); /* Link dead support -- Rantic */
        show_status( ch );
i added
  	if (ch->level < LEVEL_IMMORTAL)   /* lag for mortals on reconnect C */
	{
		  ch->WAIT_STATE( 50 );
	 }
       
Post is unread #2 May 13, 2011, 5:14 am
Go to the top of the page
Go to the bottom of the page

Quixadhal
Conjurer
GroupMembers
Posts398
JoinedMar 8, 2005

That's a solution. A better one would be to make the lag associated with spells and other intended sources be tied to the character based on time, rather than to the descriptor which gets reset when you reconnect.

The whole "wait state" system is rather brain dead, IMHO. Has anyone considered rewriting it to use cooldowns?
       
Post is unread #3 May 13, 2011, 7:15 am
Go to the top of the page
Go to the bottom of the page

Kayle
Off the Edge of the Map
GroupAdministrators
Posts1,195
JoinedMar 21, 2006


Quixadhal said:

The whole "wait state" system is rather brain dead, IMHO. Has anyone considered rewriting it to use cooldowns?


I have, but never got around to it.
       
Post is unread #4 May 13, 2011, 11:54 am
Go to the top of the page
Go to the bottom of the page

Samson
Black Hand
GroupAdministrators
Posts3,639
JoinedJan 1, 2002

That seems extraordinarily cruel to do. A wait state of 50 is pretty long, probably long enough that they could just disconnect and wait for auto-quit and have that be faster than dealing with a delay factor of 50. Plus there's no way to know if they link dropped on purpose. I can't count the number of times I've hit the wrong X on something while multitasking.
       
Pages:<< prev 1 next >>