Quote: |
All
Shark Lancaster Terrier Weasel Leviathan Spider Javelin Warbird |
Quote: |
pulled.dat
/nb.server.ini /SPAWN idblock.txt ipallow.txt ipblock.txt |
Quote: |
scrty
S Z subspace.exe Update2.exe Update1.exe Update.exe version%d\ version0 |
Quote: |
Spawned TRACERT
SUBGAME2 /SPAWN tracert %s > spawn.log SPAWN STARTED SUBGAME2 /SPAWN %s > spawn.log |
Quote: |
(SPAWN)
(FIND) (CHAT) (ENEMYTEAM:%d) (TEAM:%d) (TO:----) (TO:%s).%s> %s |
Quote: |
$login
$pvt $pub |
Quote: |
SyncJitter
AllVips TrackFlood CheckPrizeDistribution |
Quote: |
*locate
*rstat *tmode *bandwidth ?recycle ?set ?get |
Quote: |
noshutdown
*shutdown |
Quote: |
Undetermined
SOCKS5 proxy Using proxy at localhost ServerIP is not set in server.ini Not using proxy Using NAT Using custom proxy |
Quote: |
(staff)
(local) |
Quote: |
-------------------: Extended version %s |
Quote: |
To disable *shutdown create noshutdown directory to server directory. |
Quote: |
----------------------------- version 1.34.12a --------------------------------
Added proxy detection to /*einfo. Proxy is detected for Continuum 0.37 and later clients. You need to set server IP address in server.ini [Misc] ServerIP for it to work. * Undetermined - SS 1.3x or Continuum 0.36 clients * SOCKS5 proxy - User is using Continuum's built in SOCKS5 proxy * Using proxy at localhost - player is using proxy ran in same machine as Continuum client. There is no other reason to do so than monitoring or tampering with packet stream * Using custom proxy - player is using custom proxy. Suspect cheating. * Using NAT - player is using router or firewall doing NAT translation * Not using proxy - no proxy was detected between client and server |
Quote: |
----------------------------- version 1.34.12pr3 ------------------------------
Added support for team sounds. Regular users can play sounds %150 - %255 in team chat, zone sysops can upload these sounds in lvz file |
Quote: |
New command: *relkills <0 or 1> - toggles sending kills reliably on and off.
Normally server sends kill messages as non-reliable messages if killed player's bounty is less than 200 (teamkills are always non-reliable). Setting *relkills 1 will make server send kill messages reliably, New command: /*bandwidth <bandwidth> - allow to set cutback watermark per player, overriding arena's Latency:CutbackWatermark setting |
Quote: |
/nb.server.ini |
Quote: |
All
Shark Lancaster Terrier Weasel Leviathan Spider Javelin Warbird |
L.C. wrote: | ||
|
Dr Brain wrote: |
No, but you'd make it so everything under [Terrier] goes to ship 6, aka the Weasel. |
Dr Brain wrote: |
No, but you'd make it so everything under [Terrier] goes to ship 6, aka the Weasel. |
Samapico wrote: |
Uh? I would have thought it would do something like:
-[4 other ships] -Read 'Weasel' -Read the .cfg value for [Weasel] -Send that -Read 'Terrier' - ... |
Samapico wrote: |
In which case there would be no problem... So you're saying it does something like this? :
-[4 other ships] -Read 'Weasel' -Read the .cfg value for ship 6, even if it's the 5th ship we check, but just because I know we put it in a stupid 1,2,3,4,6,5,7,8 order -Send that setting with the Weasel tag -Read 'Terrier' - ... I really don't see how it could be that way |
Dr Brain wrote: |
Where does it get that section string from? As I said, there seems to be only one copy of the ship string in the binary. |