lecorsedegironde / bordeauxinternship2016game Goto Github PK

Add debug logging to the project when needed

Decouple the camera movement from the "level"

• Camera has a "target position" and a "current position" in world coordinates
• Camera has a "maximum/minimum x/y coordinates" attribute, also a max distance
• In the update loop, if distance (target position/current position) > max distance, the camera
  moves its current position to the target position.
• the camera is an observer (of an entity (player/enemy)) the camera updates its target coordinate based on the coordinates of the target entity
• The movement of the current position is limtied by the maximum/minimum x/y coordinates

Decide which of the 5 proposals you want to follow in this project, and start to think of the details of how the game will work. The Game Design Document at this point should contain four main sections described below.

Remember that this is still a living document, and will be modified as we progress with the project.

Game Idea

A high level description of the game. Its name, its characteristics, how you imagine the game to look like as you finish it, and what are the compelling points of the game.

Game description

A more detailed description of the game and its component parts. The mechanics of the game and their rules: Characters, Enemies, props, victory, defeat, etc.

Also start to make a system-level description of the game, which systems you think need to be implemented, and their relationship (controllers, characters, enemies, scenarios, resource managers, etc).

Roadmap

Make a list of features of the project (it should be very simple things such as "the player can now move the main character), and order the features as they should be implemented. Don't worry about writing down ALL features at the moment, but write down at least those which are necessary to make a prototype.

Add a reset button to avoid restarting the game at each time

Feedback can be one of multiple:

• change of color
• sound
• movement (knockback/etc) - this can be implemented by adding an acceleration vector to the entity's movement.

When player is invisible and move direction of the Troll is the opposite of the facing direction of the player, if the player hit the Troll when attacking a knock-back is applied but never removed so the speed of the Troll is augmented and he seems to be knocked back very far.

Reproduce :

• Face the Troll
• Be invisible
• Hit the Troll

Add collisions between troll and wall and between Lutin and wall

Add just a basic UI that permit to see the Life and MP level of the player

• Remember to add a "milestone" (game version) to each issue
• Remember that milestones can be changed into the future, so don't let this freeze you
• Use issues of game features to share tasks among the team

Add a basic inventory that permits :

• Changing weapon
• Seeing stats (life & MP)

Also add :

• Shortcut to access it
• UI button to access it

Create all the javadoc for the project

1. List all the features that are necessary for Milestone 0, game prototype. (Don't forget features that I did not list)
2. Start programming them!

Add a completely new weapon behaviour with all the needed attributes

Actually the drawing mechanism is handled by the GameScreen class, make the class draw themselves

Remember to close issues when you complete them :-P

This issue is completed when the two of your read it.

Review the GameScreen class and optimise the render method

Review the entire weapon system and how they're handled by MovableElements

Keep in mind that the constant should be well organized.

Create the unit tests for the code already shipped and for new code