 |
ElRui
Newbie
Joined: 19 Jun 2006
Posts: 2
|
 Posted: Mon Jun 19, 2006 6:12 pm
Lagging out issue when sending lots of commands
|
Heya, I have a spellup script that can send anywhere from 25-50 commands at one time, once it sends over 30 commands my client lags out after about 30 seconds, I can still see stuff the mud sends to me but nothing is going the other way. Any ideas? Also its not just the script if I just create an alias to send 40 items it will do the same thing.
Any help would be greatly appreciated.
Thanks!
(edit: I can send up to 30 items anything over 30 = lagout)
Using ver. 7.21 |
|
|
|
|
BlackSmith
Apprentice
Joined: 08 Dec 2002
Posts: 152
|
Posted: Mon Jun 19, 2006 6:52 pm
|
You could either use #Alarm or #Wait to slow down the feed but i would consider reducing that spamm.
Think what kind of load it generates when 10 persons like you send those commands to MUD at same time. |
|
_________________
BatMUD Best MMORPG around since 1990 telnet://bat.org:23
~ Magic & Mind beats Chrome & Meat anytime ~
Pattern(s) in PERL. Using Cmud 1.34/2.09 & BatClient. |
 |
|
|
Vitae
Enchanter
Joined: 17 Jun 2005
Posts: 673
Location: New York
|
Posted: Mon Jun 19, 2006 7:03 pm
|
BlackSmith, HE is the one that gets lagged out. The mud is not affected.
We play the same mud, with the same script and I have never had the issue that he does on either my job comp (p2 333) or home comp (p4 1.6gig) |
|
|
|
|
BlackSmith
Apprentice
Joined: 08 Dec 2002
Posts: 152
|
Posted: Mon Jun 19, 2006 7:23 pm
|
| Vitae wrote: |
| The mud is not affected. |
As long the mud process those commands, it is affected. MUD defends against this by droppping his connection. If it would not affect MUD, then why would it drop the connection?
Sending and producing lot of commands (thus lagging the mud down) usually gives you first a warning and then ticket to bannlandia or remove.
Or it might be just that that mud players likes about lag.
Sounds like your MUD has drawn a line that more than 1 command/sec in timeline of 30 sec's is considered as spamming. Like i said, try using #Wait or #Alarm. |
|
_________________
BatMUD Best MMORPG around since 1990 telnet://bat.org:23
~ Magic & Mind beats Chrome & Meat anytime ~
Pattern(s) in PERL. Using Cmud 1.34/2.09 & BatClient. |
|
|
|
ElRui
Newbie
Joined: 19 Jun 2006
Posts: 2
|
Posted: Mon Jun 19, 2006 8:14 pm
|
Its not a mud based problem because on my laptop i'm running the exact same script and there is no issue.
|
|
|
|
|
Vitae
Enchanter
Joined: 17 Jun 2005
Posts: 673
Location: New York
|
Posted: Mon Jun 19, 2006 8:51 pm
|
And as I said, I run the same script and have no adverse affect either.
|
|
|
|
|
edb6377
Magician
Joined: 29 Nov 2005
Posts: 482
|
Posted: Mon Jun 19, 2006 9:04 pm
|
try turning off echoing commands in your preferences. This may help you will find that it wont echo every command/alias it sends to the mud. It has helped in the past on a few of my scripts until i had time to properly delay things.
|
|
_________________
Confucious say "Bugs in Programs need Hammer" |
|
|
|
MattLofton
GURU
Joined: 23 Dec 2000
Posts: 4834
Location: USA
|
Posted: Mon Jun 19, 2006 9:46 pm
|
If you are still able to see stuf from the MUD, then obviously the connection is still in play and it's not a MUD issue. More than likely you are simply overwhelming your NIC card, which means you either need to restructure your script or look for new NIC drivers (worst-case scenario being a completely new card or other piece of hardware).
|
|
_________________
EDIT: I didn't like my old signature |
|
|
|
|
|
|
