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

Kicked for team killing when using this new ASP #8

Closed
frankybeans opened this issue Jan 3, 2019 · 14 comments
Closed

Kicked for team killing when using this new ASP #8

frankybeans opened this issue Jan 3, 2019 · 14 comments

Comments

@frankybeans
Copy link

@frankybeans frankybeans commented Jan 3, 2019

No one can join my server using the new ASP, they and I get kicked for teamkilling.

@wilson212
Copy link
Member

@wilson212 wilson212 commented Jan 3, 2019

@frankybeans
Copy link
Author

@frankybeans frankybeans commented Jan 3, 2019

@wilson212
Copy link
Member

@wilson212 wilson212 commented Jan 3, 2019

It's an installer already (setup.exe)

@frankybeans
Copy link
Author

@frankybeans frankybeans commented Jan 3, 2019

@frankybeans
Copy link
Author

@frankybeans frankybeans commented Jan 3, 2019

@wilson212
Copy link
Member

@wilson212 wilson212 commented Jan 3, 2019

Are you talking about the GameSpy emulator included with the Beta release? No that does not have an installer! Just this does: https://github.com/BF2Statistics/BF2GamespyRedirector/releases

@frankybeans
Copy link
Author

@frankybeans frankybeans commented Jan 3, 2019

@frankybeans
Copy link
Author

@frankybeans frankybeans commented Jan 3, 2019

@wilson212
Copy link
Member

@wilson212 wilson212 commented Jan 3, 2019

That means the player does not exist in the database the ASP uses! The script uses the PlayerID, so whatever playerId the login server is giving him, does not exist for the ASP (different database?)

@frankybeans
Copy link
Author

@frankybeans frankybeans commented Jan 3, 2019

@wilson212
Copy link
Member

@wilson212 wilson212 commented Jan 3, 2019

At this moment no, I will work on it though

@Terminal-Access
Copy link

@Terminal-Access Terminal-Access commented Jan 16, 2019

Just wanted to add my findings as I was struggling with this bug last night as well

This 100% occurs if you are using nickname prefix on your account.

Repo Steps:

  1. (Logout of BF2 if already logged in) - At the Account login screen set a Nickname Prefix (the box in the upper lefthand area of the login window) and log in.
  2. Attempt to join an online session,
  3. Observe a connection attempt that hands and eventually returns with an initial "connection timeout" error.
  4. Re-connect to the same session and observe the "you have been kicked for teamkilling" error message - this is now the default error message this will show.

Workaround:

  1. Logout of BF2
  2. Remove the nickname prefix.
  3. login to your BF2 account.
  4. Connect to your fav online session and play.

Additional Notes:
I have also noticed this issue occurs if you are using a "launcher" that passes your user account credentials upon launch e.g your using the autologin command line options.

+playerName - Set the player name
+playerPassword - Sets the player password
@wilson212
Copy link
Member

@wilson212 wilson212 commented Jan 19, 2019

Nice find! I haven't tested nickname prefixes yet. I will work on this before release.

@wilson212
Copy link
Member

@wilson212 wilson212 commented Jan 22, 2019

Fixed in the latest update (155). Commit #b4eef70

@wilson212 wilson212 closed this Jan 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants