rosalogia / bika-town Goto Github PK

Currently, if the player moves off-screen, they become invisible but are still able to move within the map. Instead, the rendered subset of the map should change according to the current position of the player. We're presented with a few obvious choices in how a solution should work:

• Have the camera move in the same direction as the player every time the player moves
• Have the camera begin moving in the same direction as the player once the player leaves an inner rectangular area of the currently rendered subset of the map

We should implement and test both approaches and see what fits best.

Problem

The game is currently single-player, but should be multi-player. We will implement a TCP server to which we'll move all the logic and state-handling from the current main executable. The main executable will then become a client which merely renders state information sent to it by the server.

This is low-priority, it doesn't really make sense to convert the single-player game to a multi-player game until it's sufficiently fully featured. At that point, development of the server should begin.

Some information like sprite locations and dimensions, window dimensions, etc. should be stored in files rather than declared in the code.

It's becoming increasingly difficult to manage the moving parts of the project without a way to conveniently say "well, all these things move in one of four directions so share this code between them, and all these things have health and take damage so share that code between them, ..."

A good solution to this problem is introducing an Entity-Component-System library, some good choices may be Legion or Specs. Legion is more up to date than Specs, but Specs is slightly more documented (in that there is a Specs book). Alternatively, we could roll our own, but we should figure out whether there's any real benefit to that before we decide to do so.

Depends on

• #1

Problem

Players have no way to view their current HP, MP, EXP, or current level. A robust system for displaying this information using the proprietary UI assets should be implemented, probably by querying the ECS for relevant information from the player in the loop.