Server Help :: View topic - Hybrid core bots

Server Help

Bot Questions - Hybrid core bots

Reaem - Sun Oct 02, 2005 10:04 pm
Post subject: Hybrid core bots

I was trying to set up a hybrid bot in chaos zone. I was given vip on the name SSBot so I could test my bot out in my private arena, but after 30 seconds my bot gets kicked.
The server tells my bot before it gets kicked that it's a continuum-only arena. I was under the impression hybrid bots were continuum-server compatible. Any ideas?
For the most part my bot runs right as it came from the hybrid website.
Any help is appreciated.

Regards,
-Reaem

Cerium - Sun Oct 02, 2005 10:29 pm
Post subject:

For clarification...

The server log has this in it, right after the bot gets kicked:
Sun Oct 02 19:23:56: Player kicked off by billing server, reason #0

Mr Ekted - Sun Oct 02, 2005 11:59 pm
Post subject:

There are no bots that act like Continuum clients. They all act like VIE clients.

Reaem - Mon Oct 03, 2005 2:57 pm
Post subject:

well,
we gave the bot temp sysop powers and it still got kicked oiff by the biller. how do i overcome this obstacle?
-Reaem

Kitsune (^) - Mon Oct 03, 2005 3:23 pm
Post subject:

put in the config:

Code: Show/Hide

ContinuumOnly=0

EDIT: Also,

Code: Show/Hide

AllowVIEClients=1

Cyan~Fire - Mon Oct 03, 2005 4:57 pm
Post subject:

IIRC, reason 0 is bad MACID or one of those default sort of kickoffs. Possible to see biller log?

Maverick - Mon Oct 03, 2005 5:04 pm
Post subject:

Reason #0 is bad machineID most of the time for bots. Just ?banfree the name.

Cerium - Mon Oct 03, 2005 9:56 pm
Post subject:

Bad macid? Anyone know the range for acceptable values?

BlueGoku - Mon Oct 03, 2005 10:47 pm
Post subject:

Mav's solution should work, I believe.

Cerium - Tue Oct 04, 2005 1:10 am
Post subject:

True, but itd be nice to know what the range is.

Update:
I believe reason #0 isnt macid. We changed the macid to one of ours (which we know is valid), set the tzb and everything to be valid, but it still dies. We even changed the bots name to make sure it wasnt on some kind of ban.

Sifted through the server log and found this:
Mon Oct 03 23:25:09: Ext: Player with invalid name tying to enter:
Mon Oct 03 23:26:09: Player kicked off by billing server, reason #0

(yes, there is no name following the first message).

Were on whichever server + biller SSC use -- so anyone familar, please fill me in.

Maverick - Tue Oct 04, 2005 3:03 am
Post subject:

I think you already know what names you can't use.
So something must be going wrong with the login sequence then. Don't know exactly.

Anonymous - Tue Oct 04, 2005 10:37 am
Post subject:

The reason #0 is Machine ID #0, if you ?banfree the bots name, that should bypass the global ban on that machine ID.

Ghost

Mr Ekted - Tue Oct 04, 2005 2:30 pm
Post subject:

Why not simply make the bot use a different MAC ID?

Cyan~Fire - Tue Oct 04, 2005 3:26 pm
Post subject:

Cerium wrote:

We changed the macid to one of ours (which we know is valid)

Cerium - Wed Oct 05, 2005 12:26 pm
Post subject:

Indeed. We already used what we know is valid, which is why Im confused. Other people using the exact same release of the core arent having this problem, which is only causing further confusion.
Sure, a banfree would fix the problem, but its only a band-aid fix. Id like to find whats causing it and take care of it once and for all.
Also, I dont have access to the biller log (if one even exists), so I dont know exactly what is going on.

Anonymous - Wed Oct 05, 2005 1:56 pm
Post subject:

Ghost, at your age, if I had the free time to pop in games and forums I would go fishing with my kid, or golfing with friends.

Seriously Alex, think about it.

Anonymous - Wed Oct 05, 2005 1:58 pm
Post subject:

I mean, it's not like you'll ever win pro without some serious breach of protocols, so why do you play nightwatch?

Cerium - Wed Oct 05, 2005 6:45 pm
Post subject:

He only saw this thread because I linked him to it, and asked him to reply. Dont count on him seeing your very clever verbal jabs.

Now do everyone a favor and refrain from replying to any text on the internet until after you have a lobotomy, fucko.

Chambahs - Thu Oct 06, 2005 10:27 pm
Post subject:

why does this person have a problem with GS anyway? and who is he? his names looks familiar but doesnt quite ring the whole bell

Purge - Thu Oct 06, 2005 10:30 pm
Post subject:

Ori = Gravitron. That should answer all of your questions.

Smong - Fri Oct 07, 2005 6:16 am
Post subject:

Cerium wrote:

Mon Oct 03 23:25:09: Ext: Player with invalid name tying to enter:
Mon Oct 03 23:26:09: Player kicked off by billing server, reason #0

(yes, there is no name following the first message).

Maybe there is a typo in a config file causing the name to be left empty? Or more unlikely encryption isn't working.

Cerium - Fri Oct 07, 2005 12:17 pm
Post subject:

Unless you mean server config file, no. The bot still logs in and functions normally for about 30-60 seconds before the server boots it.

Havent checked the encryption status though

Cerium - Sun Oct 09, 2005 11:22 am
Post subject:

Bump!?

Reaem - Mon Oct 10, 2005 9:10 pm
Post subject:

DID U CHECK ENCRYPTION STATUS YET CER????
<3,
-Reaem

Cerium - Thu Dec 22, 2005 6:19 am
Post subject:

So... I figured out what causes this, incase anyone cares.

If the bot logs in and the server has not received the registration info (sent during name creation), it will consider the player invalid. If the registration info has not been received in about 60 seconds, the server will kick the name.

As far as Hybrid goes, there was a bug causing the small 'large' packets to be sent as 0x08 and 0x09 (instead of 0x00 0x08 and 0x00 0x09), which caused the reg packet to never be received. Whoops.

grazzhoppa - Wed Jun 27, 2007 4:37 am
Post subject:

Ya old topic, but this may be helpful to people:

I was having a bot getting kicked for "Player kicked off by billing server, reason #0" too.

It was because it was sending ?chat too many times, and getting kicked by biller for command flooding. Try it yourself - spam "?chat" and you'll get kicked for flooding. Checker server log to see "Player kicked off by billing server, reason #0".

So "reason #0" can be for a bunch of reasons: macid, timezone, registration packet, and command flooding apparently.

Maverick - Wed Jun 27, 2007 5:55 am
Post subject:

reason #0 is probably used as an unknown, undefined, common reason.

Maybe it's even part of an unfinished piece of the biller where it can specify a number of reasons why it takes action against a player.