dougwl / 2hard Goto Github PK

Some of the enemy objects are colliding correctly into the screen limits but others are colliding earlier and out of the expected behavior.
We should investigate possible new ways to control how enemies should stay inside the screen.

In the last commit, we focused on the EnemyMovement class and some changes were introduced to handle unsubscribing enemies objects from GameManager 'OnModeChange' event, with the intuit of avoiding memory leaks or the garbage collector running unexpectedly.

Testing the solution, we discovered that making the object unsubscribe itself from the event throws a null reference error.

The solution found was to execute this action on the EnemyManager class and inside the ResetStart method, just before the enemies objects are disabled.
The implementation needs to be polished and applied to Survival mode , taking in consideration the new instantiated objects.

Reference:

After the last commit, enemy objects are instantiated in the beginning of the game and should be handled by enabling/disabling then when necessary.
The EnemyManager class is lacking the necessary logic to execute this behavior and should be covered with urgency.
The class Survival may still need some extra changes.