| zone22 wrote: |
| it posted wrong again
I got it for sure this time |
Code: Show/Hide ############################# ## Bot operators ## ############################# # Higher numbers on the left mean higher access privs. # Scroll down for the list of access privs. 0 :zone22 : 1 :Catid : 2 :Snrrrub : 3 :Coconut Emulator: 4 :Snarklord : 5 :Ave-iator : 6 :nintendo64 : 7 :SOS : 8 :Budger : 9 :NOBODY!!!!!!! : 10:X_IceHawk : 11:L.C. : 12:1stStrike : # Example backup passwords, for when the biller goes offline: 4 :Catid[bot] : 4 :Snrrrub[bot] : 4 :Z Bot[bot] : # 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 |
Code: Show/Hide 12:zone22: |
Code: Show/Hide ############################# ## Initial bot spawns ## ############################# Catid.Bot : +++++ : 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 Z Bot ::bot me ::AI.dll # 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 |
Code: Show/Hide ############################# ## Initial bot spawns ## ############################# Z Bot : PutYourBotPasswordHere : 0 : AI : PutYourSysopPasswordHere : ############################# ## 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 Z Bot ::bot me ::AI.dll # 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 |
Code: Show/Hide Added God-level operator: zone22 (1212)
Added SOp-level operator: Z Bot[bot] (1212) MERVBot Release Mode (Build 46) (DLL 6.7) by cat02e@fsu.edu Press any key to close this window when done. Z Bot Ext: DLL plugin connected. Z Bot Connecting zone at 127.0.0.1 port 382 Spawn with the same name already exists: Z Bot Z Bot Sending password for Z Bot Z Bot Password accepted for Z Bot. Z Bot Entering arena '0' Z Bot Re-reading arena settings... Z Bot Player entering: Z Bot #1 w/l 0:0 pts 0+0 <-- Me Z Bot Reading map file: lvl/_bzw.lvl Z Bot ERROR: Exception in plugin AI at slot 0 during event 3 Z Bot Got synchronization packet [28005623][0] Z Bot A:Showing Energy ON Z Bot A:Z Bot - Sysop - Public 0 Z Bot ^^ I Am SysOp. Hear me roar! Z Bot A:Reliable kill messages ON ERROR: Tick. ERROR: Tick. |
Code: Show/Hide ERROR: Death (move).
ERROR: Weapon handling. ERROR: Death (move). ERROR: Weapon handling. ERROR: Death (move). ERROR: Death (move). ERROR: Death (move). ERROR: Death (move). ERROR: Death (move). ERROR: Death (move). ERROR: Weapon handling. ERROR: Death (move). ERROR: Weapon handling. ERROR: Death (move). ERROR: Weapon handling. ERROR: Tick. ERROR: Death (move). ERROR: Death (move). ERROR: Death (move). ERROR: Death (move). ERROR: Death (move). ERROR: Death (move). ERROR: Death (move). ERROR: Death (move). ERROR: Death (move). ERROR: Tick. ERROR: Death (move). ERROR: Death (move). ERROR: Death (move). ERROR: Death (move). ERROR: Death (move). ERROR: Death (move). ERROR: Death (move). ERROR: Weapon handling. ERROR: Death (move). ERROR: Weapon handling. ERROR: Death (move). ERROR: Tick. ERROR: Death (move). ERROR: Death (move). ERROR: Death (move). ERROR: Death (move). ERROR: Death (move). ERROR: Tick. ERROR: Death (move). ERROR: Death (move). ERROR: Death (move). ERROR: Death (move). ERROR: Death (move). ERROR: Death (move). ERROR: Death (move). ERROR: Death (move). ERROR: Death (move). ERROR: Tick. ERROR: Death (move). ERROR: Death (move). |