Server Help

[Katie]

I had an older MERVbot core which I upgraded to 46, but I used TM_Baw, alias, and rampage plugins. Now, for only testing purposes, I left only 6 warps in the tm_baw (final will have 40). The problem is, the dll loads fine, but does nothing.

Warps.ini

Code: Show/Hide Not in code note: everthing above the first line of code was removed from the file so the example warps didn't mess with the real ones. #Ship=-1 #    ^------- Ship to warp. -1 = any #Freq=-1 #    ^------- Freq to warp. -1 = any, -2 = any public, -3 = any private # Macros you can use: #   %name%   - Name of player #   %points% - Points of player #   %squad%  - Squad of player #   %freq1%  - Freq of player. "(Private freq)" said if private #   %freq2%  - Freq of player. Private freqs are said PubAction0= #        ^--- Up to 10 actions PrivAction0= #        ^--- Up to 10 actions [Warp0] #From Astral Jump Gate 1 FromX1=15 FromY1=985 FromX2=18 FromY2=987 ToX=442 ToY=198 [Warp1] #From Astral Jump Gate 2 FromX1=22 FromY1=985 FromX2=25 FromY2=987 ToX=915 ToY=253 [Warp2] #From Astral Jump Gate 3 FromX1=28 FromY1=985 FromX2=31 FromY2=987 ToX=907 ToY=767 [Warp3] #To Astral Jump Gate/ From 1 FromX1=441 FromY1=195 FromX2=443 FromY2=197 ToX=30 ToY=1000 [Warp4] #To Astral Jump Gate/ From 2 FromX1=916 FromY1=252 FromX2=918 FromY2=254 ToX=30 ToY=100 [Warp5] #To Astral Jump Gate/ From 3 FromX1=908 FromY1=766 FromX2=910 FromY2=768 ToX=30 ToY=1000

Now I scoured the forums and found a single topic, and use it's advice by loading an empty bot and use !load. This didn't work either.

Also, my bot is exceeding the kickoutdelay 10-15 seconds after entering.

MERVbot.ini

Code: Show/Hide // WARNING: Do not copy deprecated SSBot.INI or MERVBot.INI contents here. // README.TXT has a Quick Setup guide. [Login] // If you are hosting locally to the server, please set this to 127.0.0.1 Zone=127.0.0.1:13000 // Keeps a Logins.txt file to help remember passwords RecordLogins=0 // Adjust when arena settings restrict resolution ResX=1280 ResY=1024 [Database] Spawns=Spawns.txt // The following change as in-game state changes: Commands=Commands.txt Operators=Operators.txt // Database automatic save interval (in seconds) SaveInterval=300 [Misc] // Terminal window caption WindowCaption=MERVBot terminal // Maximum number of in-game spawns (3 is absolute maximum for remote zones) MaxSpawns=3 // Mask ban information so it remains constant but different from your own MaskBan=0 // Allow players to send .WAV files to the bot (not stored on disk) PlayerVoices=0 // No terminal output. This will speed up the bot noticeably NoTerminal=1 // Ignore commands in public chat? It gets annoying if these aren't ignored DisablePubCommands=1 // Enable this if the bot is not seeing everyone fast enough NoisySpectator=0 // Maximum number of failures while logging-in before giving up MaxConnectionTries=5 // Initial billing network ?chat channels InitialChatChannels= [Security] // Log chatter to BotName.log (slow diagnostic tool), turn off when not using it! ChatterLog=0 // Should I listen to (possibly spoofed) remote private messages? RemoteInterpreter=1 // If so, should I listen to remote private messages from passworded operators? RemoteOperator=1 // Encrypt network traffic? (required sg1.34.12+) EncryptMode=1 [Registration] // Change these if the bot has trouble creating new accounts Name=Catid Email=cat02e@fsu.edu State=Florida Age=19

and spawns.txt (I don't care if you see the pw/s, it's only a testing zone)

Code: Show/Hide ############################# ##   Initial bot spawns    ## ############################# Astral-Bot  :  loki  :  0  : alias, rampage, tm_baw :  solstice : ############################# ##  Spawns.txt reference   ## ############################# # This file is part of the MERVBot database collection. # Changes made while the bot is running will NOT be lost. # Lines beginning with non-alphanumeric characters ('#', '$', etc) are comments. # Spawns: # In this file you specify the name(s) your initial bot(s) # will use, and what its/their staff password(s) will be. # WARNING: As a rule of thumb, you can never host more than 3 bots in one zone, #          unless the bot is hosted on the same computer as the subspace server. # Spawns.txt Format: # Bot name : Bot password : Arena name : Plugin names : Staff password : Creation string # NOTE: creation string shoudl always, always, always, always be of the following format: # dll_name parameters|dll_name parameters|... #

Last but not least operators.txt

Code: Show/Hide ############################# ##      Bot operators      ## ############################# # Higher numbers on the left mean higher access privs. # Scroll down for the list of access privs. 4 : VampireZ : botop 5 : Ronove   : botown # Example backup passwords, for when the biller goes offline: # Remove these before you make your own operators. ############################# ## Operators.txt reference ## ############################# # NOTE: I suggest using blank passwords for all your operators. #       Create backup names WITH passwords in case the biller goes down. # This file is part of the MERVBot database collection. # Changes made while the bot is running WILL be lost. # Lines beginning with non-alphanumeric characters ('#', '$', etc) are comments # Operators: # This file is used for defining who has access # to bot commands from inside the game. # These people are called "operators" who are assigned # passwords used with the !login <password> command # to gain access.  I recommend erasing example # operators above, before running the bot. # Types of Operators: # LVL Type           Description # 0   Player         Requests information services # 1   Limited        Player with some privelages # 2   Moderator      Represents player interests # 3   SuperModerator Manages moderators # 4   SysOp          Represents staff interests # 5   Owner          Changes internal bot settings #...  (Etc)          Other ways to say "Owner" # Operators.txt Format: # Access level:Name:Password # 2:Catid:Password  <- !login Password required # 2:Catid:          <- !login Password NOT required # Blank Passwords: # A blank password means operator is granted powers upon entering the arena, # and does not need to use !login unless his powers change while he is still # in the game. # White-space: # White-space (' ') is ignored before and after colons (':') # Ex. 5 : Catid   :   Password  is the same as 5:Catid:Password

Those who take the time on this have my upmost appreciation.

[Smong]

Does it enter the arena, or doesn't seem to get into the zone at all?

[Katie]

It enters, but then 10-15s later, when I'm also in game (or when I'm not) it'll give the exceeded kick out delay error.

[Katie]

I forgot to mention the client issue. Here's the specs on the pc I use to run my server:

System:
Microsoft Windows XP
Home Edition
Version 2002
Service Pack 2

Registered to:

XXXXX XXX
XXX XXXXXXXX
XXXXX-XXX-XXXXXXX-XXXXX

Computer:
AMD Athlon XP 2000+
1.67 GHz, 512 MB of RAM

However:




Small image sorry, but you can see that CPU usage is 100%!!!

Subbill = 13%
Subgame2 = 16%

And, some odd system process called csrss is taking up 56%, what in the hell is csrss?

[Katie]

EVERYONE SHOULD SEE THIS

[Solo Ace]

Uh, almost every system service in Windows would give warnings like those.

[Bak]

your bot might be going into an infinate loop somewhere

[Katie]

Would I be better off scrapping the entire MERVBot and starting over?

[Quan Chi2]

I think you should just reformat and take out all the parts from your CPU, and put them back in in different order.. Mabye you could then tell the forum if this helped or not...

[Cyan~Fire]

No, scrap subbill, it is known to use up huge amounts of system time in both itself and csrss.exe (which only makes sense). Use SSB2. Neither of them is as efficient with CPU time as possible, but at least SSB2 only iterates 4 times per second when compared with subbill, which iterates as often as possible. Maybe some day I'll upgrade SSB2 to iterate less but receive packets immediately. Hmm.
_________________
This help is informational only. No representation is made or warranty given as to its content. User assumes all risk of use. Cyan~Fire assumes no responsibility for any loss or delay resulting from such use.
Wise men STILL seek Him.

[Quan Chi2]

Just unplug everything

[Assassin2684]

Why dont we just unplug you?

[Quan Chi2]

because you can't.. I'm not a machine

[Zim]

I loaded up your warps.ini into my bot to see how it'd react (merv .46) and got these errors:

yt Ext: DLL plugin connected.
yt Ext: Invalid warp.ini entry: 0
yt Ext: Invalid warp.ini entry: 1
yt Ext: Invalid warp.ini entry: 2
yt Ext: Invalid warp.ini entry: 3
yt Ext: Invalid warp.ini entry: 4
yt Ext: Invalid warp.ini entry: 5

I took a look at baw's src and if any of the ini values for an entry are not numeric(or not there) it'll kick out that entry. to fix that i just added to each entry:
Ship=-1
Freq=-1

after that baw seemed to play nice for the little bit i played with it. you may just have a different version of baw then me. who knows.

as for the timeout thing i think bak is right. any badly coded loop would drive mervbot's cpu usage thru the roof and timeout the bot. upgrading cores could have(shouldn't but could have) trigger it.

to figure out which is the naughty plugin load the bot without any plugins. let it sit there for a minute or 2. .help it to make sure it is alive and well. then .load one and only one plugin. let that plugin do it's thing for a few minutes. .help the bot and make sure it's still there. if everything goes well .load another of the plugs, test, rinse, repeat. when one finally does lock up the bot you'll know where the bug is.

[Katie]

Well it turns out that yes, I failed to add the ship & freq sections, but even that didn't help.

What I failed to notice was the MervBot client saying INVALID OWNER. Which was causing it to go into an endless loop, and eventually disconnecting itself. Now it works fine, but what I had to do was in Operators.txt, just insert my name on the list where I want it. So any of the others, should they ever come to my zone, will have access to the bot. It works, and it's only a test zone, so I don't care.