Dkim/modify game screen

[dooki114]

Description

• Bug fixed

  Constant names in agent_v_agent_demo.py fixed (Agent -> Ally) Assertion Error from env fixed

• BGM ON/OFF toggling by user input, 'B' on the keyboard

  Only supporting the player mode BGM plays by default toggle_bgm(): toggles self.bgm_switch at every valid user input (B), and either plays or stops the BGM accordingly. update_bgm_state(): render the current state of BGM (ON/OFF) on pygame screen font called 'bradleyhand' from pygame was used and was implemented to turn Red when ON and Blue when OFF

• GUI re-arranged (horizontal -> vertical)

  Enemy Kill log and BGM status have been moved above the board Ally Kill log and Timer have been moved below the board font called 'cochin' from pygame was used for the following strings, . -> "Ally Kills: " -> "Enemy Kills: " -> "Timer: < time left >" (temporarily deactivated)

• Overall design has been updated to make the fullest use of the remaining spaces.

  draw_background(): since the code for the compartment lines became a bit too long, I just put all of them and back_ground setting together into one method

Type of change

• [o] Bug fix (non-breaking changes which fixes an issue)
• [o] New feature (non-breaking changes which adds certain functionality)
• [] Documentation update (updating documentations)
• [] Breaking change (fix that breaks existing functionality)

How has this been tested?

• Local env
• Travis CI

[hojoungjang]

@tanliyon Actually, I'll do it here.

So basically my idea was to expose just the step_user() method and users/developers can create whatever custom game mode loop they want just like how step() method is used in every gym environment. Developers create their own training loop with the environment's exposed methods and let their agents interact with the environment.

So that was my idea with game mode implementation and with this we do not have a clear way to insert "GAME OVER" message because the program execution will immediately jump back to the users' code and not our code once the game is finished. Hope this part was clear.

But then, in our last meeting, you brought up the idea of implementing the game mode on our end and wrapping and exposing the game mode itself as an executable application with command line arguments right? In that case I think we can easily add the "GAME OVER" message.

[dooki114]

As we agreed in our previous discussion, Timer has been temporarily deactivated, and is not being displayed on the screen. Once our discussion on "Game Over" settles, I'll make more revisions!

[tanliyon]

Ahh I see what you mean @hojoung97, yea I agree with your idea. So for now I guess we can remove it, and later on we can add it into the game_mode executable.

[hojoungjang]

Yup sounds good, so let's leave the game_over() method in xiangqi_game.py for now since we might use it later