How wenshen18643/fit2099 works
Project type and purpose
• This is a Java-based game engine library (package edu.monash.fit2099.engine) with three demo “worlds” (Conway’s Life, Forest, Mars) and a student-built game (package game).
• Its purpose is to provide a reusable framework for turn-based grid games: managing world state, actors, behaviours, actions, items, ground types, displays, etc., and then demonstrate its use via demo applications and the assignment game.
File structure
Top-level
• docs/ – design and demo screenshots
• src/edu/monash/fit2099/engine/… – core engine library
• src/edu/monash/fit2099/demo/… – three demo modules (conwayslife, forest, mars)
• src/game/… – student’s assignment game
Key engine subpackages (core abstractions)
• positions – World, GameMap, Location, Ground, Exit, DefaultGroundCreator, NumberRange
• actors – Actor, Behaviour, ActorAttribute, BaseAttributes, ActorLocationsIterator
• items – Item, PickUpAction, DropAction
• actions – Action, ActionList, DoNothingAction, MoveActorAction
• capabilities – Status
• weapons – Weapon, IntrinsicWeapon
• displays – Display, Menu, Printable, UpdatePageAction
README
• The README contains only project title ASCII art. No architectural details beyond being a FIT2099 assignment.
Elements
– Clear labels for: Engine Core, Demo Modules (Conway, Forest, Mars), Game Module, Application entry, Console I/O
• Engine ← Demo/Game (dependency/inheritance)
• Application → World → Display → Actors → Behaviours → Actions → World (data/control flow)
• Engine core (blue rectangles)
• Demo/Game modules (green rectangles)
• Application entry points (orange circles)
Dependencies and associations
– Between engine subpackages: e.g., actors use positions; actions operate on actors and positions; displays consume Printable from actors/ground/items.
– Between Demo/Game and engine: e.g., MarsDemoApplication extends nothing but uses GameMap, Actor, Behaviour, ActionList.
– Between modules: no cross-demo dependencies (demos are independent).