Methias

CELEBRATE w000t w000t. Got a bot up. :-) Newer version of map meteorwars.lvl

Whats the <3 for? <3 something of mine? lol

WAA SOMEONE GET ON SUBSPACE. IM ALL ALONE lol

Someone come vist me in my zone. Im bored T__T.

Yeah its online. I just turned it on

Thank you Default+. And Purge. I know im the best mapper ever. LMMFAO.

5 people downloaded it but no one is posting WTF?

I got a friend who had a Zone before, so hes just gonna send me his. Thanks for your help anyways.

WOOO !!!!! Got a bot to work now

Anyone like it?

YES! It works. Sorry for bothering you guys. I guess it just needed more than 2 people

Hey, im gonna upload the map that i made for my new zone. Take a looka t it and tell me if you like it.meteorwars.lvl

That is correct. Im in the game messing with the settings. These are my king settings : [King] DeathCount=1 ExpireTime=15000 RewardFactor=1000 NonCrownAdjustTime=3000 NonCrownMinimumBounty=50 CrownRecoverKills=3

There is nothing on that site saying what numbers to put in the slots. It just says what the option is.

AllowVIEClients=1 //If you wish to restrict your zone to continuum only, set to 0. If you want everyone to play, set to 1 ForceContinuumOnly=0 //If set to 1, will only let continuum users enter zone AllowPrerelease=1 //Set to 1, people with newer continuum can enter. Set to 0, only current client will be allowed in Those are the settings. Should i change anything?

Yes i looked at that. But what do the settings have to be set to for King to work. Do i have to disable flags? What numbers do i put in the king options?

How do i set those settings up? I went into my cfg and dont know what to put there.

I see in SWZ, and a few other places that they have King Of the Hill running, do you have to have a bot for that to work?

It says its not being allowed in. Although i have it on all the staff .txt's. And vip.txt

############################# ## Bot operators ## ############################# # Higher numbers on the left mean higher access privs. # Scroll down for the list of access privs. 1 :: 2 :: 3 :: 4 :Rawr: 5 :Methias: 6 :Flag B0T: 7 :ServerHost: 8 :Yami Peps: 9 :: 10:: 11:: 12:: # Example backup passwords, for when the biller goes offline: Yekoms # 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 !@#$%^&*igned # passwords used with the !login 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 ############################# ## Initial bot spawns ## ############################# Flag B0T: yekoms*yekoms : 0 : alias, flag, rampage : yekoms*yekoms ############################# ## 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|... # # Example: flagbot -f=4 -t=10|aliasbot -m=0|goalkeeper goals=2 # # Only bots that explicitly support the creation string will be able to use it # 0. Bot names will be checked for validity prior to connecting. # 1. Bot passwords and arenas may not contain a colon (':'). # 2. If staff password is blank, the bot will still attempt to use it. # 3. Bots do not append staff password to name password, in other words # it is safe to change staff position of an older bot. # 4. Staff passwords are case-sensitive and shouldn't start with *. # 5. Separate the plugin names with commas: CTF, ELIZA, ALIAS # 6. Other login settings are defined in the INI file. # White-space: # White-space (' ') is ignored before and after colons (':') # Ex. 5 : Catid : password is the same as 5:Catid:password // 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:7000 // 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=0 // 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=0 // 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 Its not logging in. I dont know what im doing wrong.

Gah ill keep this in mind. Im not gonna use a bot. too complicated lol Any place on here willing to host my Zone?

Re-read Settings: 0 ms Connection request from: Cheez00r Bot Tue Nov 01 16:40:02: Cheez00r Bot> SYSOP LOGGED IN Connection status read as terminated: Cheez00r Bot Thats what i get when i try to log my bot in with MERVbot. ############################# ## Initial bot spawns ## ############################# Cheez00r Bot : yekoms*yekoms : 0 : alias, flag, rampage : mod : ############################# ## 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|... # # Example: flagbot -f=4 -t=10|aliasbot -m=0|goalkeeper goals=2 # # Only bots that explicitly support the creation string will be able to use it # 0. Bot names will be checked for validity prior to connecting. # 1. Bot passwords and arenas may not contain a colon (':'). # 2. If staff password is blank, the bot will still attempt to use it. # 3. Bots do not append staff password to name password, in other words # it is safe to change staff position of an older bot. # 4. Staff passwords are case-sensitive and shouldn't start with *. # 5. Separate the plugin names with commas: CTF, ELIZA, ALIAS # 6. Other login settings are defined in the INI file. # White-space: # White-space (' ') is ignored before and after colons (':') # Ex. 5 : Catid : password is the same as 5:Catid:password Thats what my spawn.txt looks like. ############################# ## Bot operators ## ############################# # Higher numbers on the left mean higher access privs. # Scroll down for the list of access privs. 1 : : 2 : : 3 :: 4 :Rawr: 5 :Methias: 6 :Cheez00r Bot: 7 : : 8 : : 9 : : 10: : 11: : 12: : # 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 !@#$%^&*igned # passwords used with the !login 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 Thats what my operators.txt looks like.

Well i downloaded MERVbot and im gonna set it up right now. Ill get back with you with the results Ugh. This needs brainpower. I dont have any at 3:21 AM. Ill try to set this up in the morning. Im just gonna go hang in SWZ right now.

I know i really have no say in anything cause i dont know any code or anything. And not like my word really matters, but i think you guys have a great idea. And im sure it would become successful

Looks abit complicated. Does anyone know of just a bot. Just 1 bot. For like the main arena. Cause TWcore has a !@#$%^&*load of them. And also, is there a program to make the F1 thingie look cool?