prophets-of-profit / galactic-rush-old Goto Github PK

When running the game on Android, if the game is open and home/back is pressed, and then the game is resumed, a lot of textures are gone. It seems like using an AssetManager in Main should do the trick according to https://github.com/libgdx/libgdx/wiki/Managing-your-assets#resuming-with-a-loading-screen, but I'm not sure, and we'd need to implement this first. Regardless, we should be using an AssetManager as it seems that that is good style in LibGDX and AssetManager handles a lot of asset management correctly.

Would it be nice to have an event log ui element to show what actions each drone has done while the animations for droneturns are going on? I think it would be nice for seeing what is actually happening. This could even be further extended to allow players to see event log messages pertaining to specific drones or bases to see a 'history' of what the drone/base has done/has had done to it.

The Menu Button has as much importance visually as the submit changes button. This shouldn't be the case because the submit changes button is a gameplay button and should be more important, whereas the menu button is more of a 'meta' button that brings up a menu that isn't pertinent to gameplay. I think this could be fixed by changing menu button from a text button to an image button using a pause icon.

Because destroying the enemy HomeBase is the victory condition for this game, we need to declare the game victor when the enemy homebase is destroyed.

According to https://github.com/libgdx/libgdx/wiki/Scene2d.ui#changeevents, using ChangeListener would be preferred over using ClickListener for buttons.

The window should also have a border of transparency so we can drag it without momentarily panning.

This can be done through storing draft state in Game and storing changes in draft state in Change. As a feature, this is quite necessary.

Selection highlights in the same color as labels, so it does not appear in the drone selection UI element.

I think a good way to do behaviour for modal popup windows would be to draw a thin gray layer over everything on the screen to make it non-interactive and then overlay a modal on top. This would solve issue #13 because it would mean only the modal window can be interacted with while active. However, the issue with this approach would be that the background cannot be interacted with, so for example, players cannot see planets while modifying drones.

Right now, drones can be created, but there is no way to actually give them instructions and/or modify them. As a feature, this is quite necessary.

Using a list prevents us from using lists for anything else

This means handle as much as possible on the host side in order to ensure the changes are actually possible given the player's resources.

We can fix this by automatically ending the game if the host leaves, or by assigning a new host. See #2

This should make the galaxy more structured and look nicer, avoid unnecessary hardcoding, and prevent it from being stuck in a rectangle.