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.

Sign up for GitHub

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

Jump to bottom

ETe server/ded not compatible with ET:Legacy? clients #66

Closed
ensiform opened this issue Jul 30, 2021 · 4 comments
Closed

ETe server/ded not compatible with ET:Legacy? clients #66

ensiform opened this issue Jul 30, 2021 · 4 comments
Labels
Priority: Critical Status: Available Type: Bug
Projects
Progress Tracking

Comments

@ensiform
Copy link
Member

Triggers CL_ParseServerMessage: Illegible server message 13 during connect with 2.60b or legacy client on our server.
@ensiform
Copy link
Member Author

ensiform commented Aug 1, 2021

Closing. Was related to lack of sv_pakNames.

@ensiform ensiform closed this as completed Aug 1, 2021
@ensiform ensiform reopened this Aug 1, 2021
@ensiform
Copy link
Member Author

ensiform commented Aug 1, 2021

Now only happens on ET:Legacy clients 🤔

@ensiform ensiform changed the title ETe server/ded not compatible with vanilla clients ETe server/ded not compatible with ET:Legacy? clients Sep 8, 2021
@ensiform ensiform added this to In progress in Progress Tracking Jan 30, 2022
@Aciz
Copy link
Collaborator

Aciz commented Nov 12, 2023

When ET:Legacy client initiates a download from an ete-ded server, it will trip in CL_CGameBinaryMessageReceived in a following scenario

  • Client doesn't have the mod installed which the server has (e.g. older version present locally compared to server)
  • Client hasn't loaded cgame vm yet (fresh boot into menu, so only ui vm is loaded)

https://github.com/etlegacy/etlegacy/blob/985e61bec8ae7f972635b19e9233250bfd320f81/src/client/cl_cgame.c#L559-L572

ETe client will return here instead of throwing an error, and 2.60b just doesn't do any checks and does a VM_Call always. However the following scenario does not occur on etlded/2.60b ded, so it's reasonable to assume it's something specifically that ete-ded does differently, which causes this issue.

@Aciz Aciz mentioned this issue Nov 12, 2023
Merged
@ensiform
Copy link
Member Author

Probably can close this now so I am going to.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Priority: Critical Status: Available Type: Bug
Projects
Progress Tracking
In progress
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ensiform @Aciz