Arsenal - Make Zeuses able to save, delete, and edit Default Loadouts #9278
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
|
Tested in SP and Eden, no idea if MP'll work (it should?). |
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.
When merged this pull request will:
globalparameter toFUNC(addDefaultLoadout).FUNC(addDefaultLoadout)internally.FUNC(removeDefaultLoadout)andFUNC(renameDefaultLoadout). What it says on the tin.Loadout index in the local loadout save events remains the same, but that whole behavior's weird with default loadouts.
Loadout save/delete events aren't fired remotely in MP.
Doesn't have the same handling as public loadouts. Should it? I don't think there's much issue with the list not being updated until the player changes tabs. Default loadouts shouldn't be getting updated that often.
IMPORTANT
Component - Add|Fix|Improve|Change|Make|Remove {changes}.