Energy: Fix Amber not Generating Particles #1061
Merged
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
ghost
merged commit 
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.
Description
This PR adds a simpler way to get the originally owning entity of an
EntityClientGadget. The gadget itself now knows who the original owner was. This simplifies some code inEnergyManager, and simultaneously fixes the problem with Amber not generating particles (which was caused by one gadget in the chain already being destroyed and therefore no longer existing in the scene when the client invokedABILITY_ACTION_GENERATE_ELEM_BALL).It also does some refactoring of
EnergyManager, sincehandleGenerateElemBallwas getting pretty long.Issues fixed by this PR
Type of changes
Checklist: