Skip to content

Pallet Town 0.5 [PT-000]

No due date 0% complete

Description:

This milestone will represent the first leap from scratch to simple movement around the outside of Pallet Town. The aim will be to implement player movement around the outdoors setting of pallet town (cut off before the grass patches).

This milestone is quite important because it should set up the code for future enhancements so that implemen…

Description:

This milestone will represent the first leap from scratch to simple movement around the outside of Pallet Town. The aim will be to implement player movement around the outdoors setting of pallet town (cut off before the grass patches).

This milestone is quite important because it should set up the code for future enhancements so that implementation is modular and consistent throughout the game. A lot of design decisions will need to be made as far as room, player, and other various core implementations go. It might be a good idea to look into creating a database or xml-parsing system for easy switching out of rooms, sprites, etc.

Required Goals:

  • implement a room object
  • implement a player object
  • implement an npc object
  • utilize and enhance the core to be able to use the above objects with given sprites
  • enhance the core to animate movement and detect walls / npcs

Optional Goals:

  • dynamic (moving) npcs
  • npc text interactions
  • controller D-pad + A-button support
  • implement music
  • implement / start construction of a database for modular image/ sprite/ collision control
    • the idea would essentially be to paint a "smart" canvas via xml or something

Notes:

  • for each new object created, a unit test file should be created and implemented to ensure functionality
  • the optional goals aren't necessary, but they should be on your mind for future dev
  • the deadline is obviously not a hard-set one, but it'd be great to get this done in a month
  • some of the dev will need to be done on the master branch for organization of folders and code etc
  • most of the dev should be separated into branches which utilize appropriate labels
Loading