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

Suite Version Tracking: Adding Full Versioning and Version Protection in MegaMek #3162

Merged
merged 5 commits into from Oct 1, 2021

Conversation

Windchild292
Copy link
Member

This moves Version to be tracked based on a constant across the suite, and expands incorrect version protection. This will prevent any issues relating to loading a save file from a previous version, provided the file does serialize first (which would require changes to MegaMek file I/O... but would fail anyway) and isn't from the same dev snapshot. It also prevents any issues from joining a server of the wrong version. It does not handle within a snapshot, which may or may not work based on the current changes to the Game class.

Once this is merged I'll update the build document on the wiki, as it reduces the number of version text changes required from 6 to 4.

@lgtm-com
Copy link

lgtm-com bot commented Sep 22, 2021

This pull request fixes 2 alerts when merging df4c5cf into 2c9538b - view on LGTM.com

fixed alerts:

  • 2 for Potential output resource leak

@Windchild292 Windchild292 merged commit 5d9db04 into MegaMek:master Oct 1, 2021
@Windchild292 Windchild292 deleted the dev_Windchild_Version branch October 1, 2021 14:00
@Windchild292 Windchild292 mentioned this pull request Oct 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug (RFE) Enhancement Requests for Enhancement
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants