first iteration of locking enemy data / readonly mode #94
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
First attempt at a very dumbed down version of a read-only mode related to issue #67. Once enemy/route data is cleaned up we can hopefully add a reference to which pull an enemy belongs to in the |
srenauld
requested changes
Jan 4, 2021
|
@srenauld thank you for the suggestions. I removed the setting from the addon DB and I also refactored some of the code to make it more scalable (ReadOnlyMode) as I'm sure there will be more than just locking the enemy's placements in future releases for Read Only mode. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.