ishadijcks / lands-unknown Goto Github PK

Features

• Parse content from Yaml
• Validate against zod input schemas
• Generate JSON schema from zod
• Compile into single gameData object adhering to zod output schema

The current method of intercepting the shutdown does not seem to save every player

Use Zod for schema validation to check client requests.

Skills is a relatively easy feature that can be used to setup the entire Feature architecture.

Add Activity Queue system

Add a local store using sqlite, and a remote one using fire/supabase

Currently the userId is used as token, if it ever leaks we can't change it so it's better to use JWT instead.
Then we can login from the client, grab a token from Supabase and decode that on the server

Decide on what should be in the initial release

Scaffolding

• Repo structure
• Tests
• CI
• Deployment

Engine

• User authentication and persistence
• Communication validation
• Basic Content parsing

Core

• Activity Queue
• World Map
• Basic items
• Inventory #10
• Key Items
• Facilities
• Skills #5

Content

Skills

• Mining
• Fishing
• Foraging
• Woodcutting
• Smithing
• Cooking

WorldMap

• Initial city + Port

Art

• Items
• NPCs
• World Map

Things that won't be in the initial release

• Combat
• Equipment
• Enemies
• Recipes
• Dialogue
• Quests

Quests

• Mining/Smithing introduction
• Fishing/Cooking introduction
• Basic fetch quest

Items should be fungible, can be stored as a map of Hrid => amount