-
Notifications
You must be signed in to change notification settings - Fork 3
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
Columns that are missing in old clients #25
Comments
|
Turns out this wasn't the same sort of bug, but an entirely different class that should be fixed now |
I think this issue can be closed as we now have the oldest client in our possession up and running with lu-explorer |
Are there still warnings in the logs? The current code just doesn't crash under any circumstances, but that doesn't mean it doesn't try to read those columns anymore. (ie paradox-typed-db is more forgiving now, but will still complain the server is calling it wrong) |
oh right! I'll grab those logs and document what it is complaining about |
These are the ones I see in logs
|
We use
paradox-typed-db
based on 1.10.64, but we want ParadoxServer to work with old clients ideally. This issue is to track columns that were added recently that we should ignore completely if missing:Activities:gate_version
DeletionRestrictions:gate_version
DestructibleComponent:factionList
ItemComponent:commendationLOT
MissionTasks:gate_version
Objects:_internalNotes
Objects:gate_version
The text was updated successfully, but these errors were encountered: