Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

8301951345

4
Posts
1
Topics
A member registered 4 days ago

Recent community posts

(2 edits)

Day 3

Added the makings of a basic Entity-Component architecture focused on flexibility and usability. 

Added skeleton of a HUD around the game viewport that listens to changes in the player's relevant state. 

Added a first pass at a rudimentary inventory menu for debug usage. 

Tomorrow (or late tonight), I hope to add a few items and the ability to pick up items from the map and place them in inventory, or drop from inventory onto the map. That will be the beginning of interactivity in the game world, as currently it involves nothing except walking around an empty "ship".



Day 2.5

Refactored data structure for cells, added some infrastructure to support flexible entities, added dummy player and player movement.



Day 2

Added barebones procedural generation for empty, boxy ships, which is the skeleton for adding more interesting generation later. Added utilities for RNG, iterables, and slightly better control over tile attributes.

Next steps are adding player, player movement, and collision detection.





(2 edits)

Untitled roguelike. Codenamed EspressoCream.

Posting here for motivation.

This is my first game. I'm coming from background in machine learning. Just learned Dart last month and have been picking at Rust for a year or so on and off.

Working with no game engine and no game-specific frameworks or libraries. Building a UI system on top of Flutter. Plan to code game logic in Dart. Expensive graph algorithms or AI models will be written in Rust if needed, but probably won't get that far given time constraints.

Day 1: Created a core UI. Added dummy map. Implemented ability to read user keyboard input, route it into the game logic, operate on it, then call UI updates as needed. Happy with the appearance. Happy with separation of concerns.