Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to add bot to unrated game with no title restrictions #202

Closed
theblankman opened this issue Apr 22, 2014 · 2 comments
Closed

Unable to add bot to unrated game with no title restrictions #202

theblankman opened this issue Apr 22, 2014 · 2 comments

Comments

@theblankman
Copy link
Collaborator

Tried to play an unrated game against a bot, the bot could not join. Salvager v2.5.4.0 beta. Bot could join with Salvager 2.5.1.6.

JS Console output:

Uncaught Invalid server message type: ADD_EXTUSER connection.js:101
Uncaught Invalid server message type: REM_EXTUSER connection.js:101
2
Uncaught Invalid server message type: REM_EXTUSER connection.js:101
Uncaught Invalid server message type: REM_EXTUSER connection.js:101
Uncaught Invalid server message type: REM_EXTUSER connection.js:101
Uncaught Invalid server message type: ADD_EXTUSER connection.js:101
Uncaught Invalid server message type: ADD_EXTUSER connection.js:101
Uncaught TypeError: Cannot read property 'ratingPro' of undefined autokick.js:32
3
Uncaught Required parameter missing and has no default.  Message = InviteBotTableToken, parameter = token due to token not a string FSSDK.js:11917
2
Uncaught Invalid server message type: ADD_EXTUSER connection.js:101
Uncaught Invalid server message type: REM_EXTUSER connection.js:101
Uncaught Invalid server message type: ADD_EXTUSER connection.js:101
GS.WS.conn.onmessage connection.js:101
Uncaught Invalid server message type: REM_EXTUSER connection.js:101
GS.WS.conn.onmessage connection.js:101
@aiannacc
Copy link
Owner

Good catch. Thanks for reporting it.

It looks like the problem is the pro rating cache I created. Players only get added to it when they enter the lobby, so bots get skipped and you get "undefined" when you query the cache for them.

Probably the easiest fix is to move the opp.get('isBot') check to the top of the autokick callback and just short-circuit the whole process.

@michaeljb
Copy link
Collaborator

Fixed in #205

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants