Dev Guide
WebsiteGitHubGitBook
  • 📝Dev Intro
    • Using GitHub
    • Using Unity
    • Licensing
    • File Naming & Organization
      • File Naming
      • File Organization
        • Object Type
  • 📡Networking
    • Introduction to Game Networking
    • FishNet Networking
      • Server
      • Client
      • Server RPC
      • ObserversRPC
      • Network Message
  • 🖊️Guidelines
    • The C# Style Guide
      • Nomenclature
        • Namespaces
        • Classes & Interfaces
        • Methods
        • Fields
        • Parameters
        • Delegates
        • Events
        • Misc
      • Declarations
        • One declaration per source file
        • General class structure
        • Access Level Modifiers
        • Spacing
        • Brace Style
        • Switch Statements
        • Language
        • Common Patterns and Structure
          • Applying attributes on all network related methods.
    • Code Design Definitions
      • Actor
      • System
      • View
      • Events
        • Event Bus
        • Action
      • System Locator
      • Tweening
    • Asset Criteria
      • External Criteria
        • Animations
        • Fonts
        • Models
        • Textures
        • Graphics
        • Audio
      • Importing Criteria
        • 3D Models
        • 3D Animations
        • Textures
        • Graphics
        • Audio
      • Internal Criteria
        • 3D Models
        • 3D Animations
        • Textures
        • Graphics
        • Audio
    • SS3D's coder good practices
    • Code design patterns
  • 📖Guides
    • Application Settings
    • Running the Project
      • Configure your firewall and antivirus
      • Building the game
      • Joining a server
      • Hosting a server
      • Setting up a dedicated server
    • Debugging SS3D
    • Maintainer Guide
      • Pull request review process
    • Testing SS3D
      • Assets audit tests
      • Edit mode tests
      • Play mode tests
        • Inventory test
        • Health tests
    • Working with animations
  • 🛣️Roadmap
    • Releases
Powered by GitBook
On this page
  • 0.0 - Rework
  • 0.1 - Minimal Viable Product (MVP)
  • 0.2 - Alpha: Expand The Basics
  • 0.3 - Alpha: More Systems

Was this helpful?

Edit on GitHub
Export as PDF

Roadmap

The progress bar of Space Station 3D.

PreviousWorking with animationsNextReleases

Last updated 1 year ago

Was this helpful?

We use milestones to track large achievements of development. Our tracks the individual tasks in our active milestone(s). The milestones are defined below.

Purple - indicates the milestone is completed. Green - indicates the milestone is in progress. Yellow - indicates the milestone is on GitHub but NOT in progress yet. White - indicates the milestone is only be theorized at this point and will be elaborated on in the future as we get closer to it.

Reminder that our milestones are synced with our release versioning for easy tracking, link below.

(We will add GitHub links to the name of the milestones in the list below as they get added to GitHub.)

0.0 - Rework

The rework is the first primary milestone. Its goal is to rework the structure (underlying aspects) of the game (such as networking, tilemaps, character movement, etc.), harmonize contributor guidelines and workflows, and porting over necessary systems.

0.1 - Minimal Viable Product (MVP)

The MVP is the goal to achieve a basic demo-like product to showcase a glimpse of our future game. It should include basic health & combat, crafting & construction, clothing, and shuttles.

Basic Health
Basic Combat
Clothing

Basic clothing system. The belt cannot be put on if the player is not wearing a jumpsuit, and the jumpsuit cannot be removed until the belt is removed first.

Basic Crafting
Basic Construction

Basic construction should be somewhat easy i would think. Its something we have had in the past so maybe could use that as reference, also we have in-game tilemap editor so basically it would just be 'hide the editor from non-admins and add some tool interactions similar to that on the develop branch'

Additional Roles

I agree its not vital but I kinda see these helping with showcasing basic systems. If we have basic health, may as well add a room and clothing and role for it. Bartender represents basic substances, security represents basic combat, assistant represents basic item crafting, engineer is basic construction, captain can 'call the shuttle' to end the round.

Finalize MVP

0.2 - Alpha: Expand The Basics

When we really start to expand systems, add interactions, new content etc..

Basic NPCs
Expand Interactions & Containers

Expand Gamemode & Rounds

Expand Gamemodes:

Expand & Fix Tilemaps
Expand Health & Combat

Expand Health:

Expand Combat:

Expand Crafting & Construction

Expand Item crafting:

Harmonize Clothing & Character Movement

Clothing:

Character Movement:

Polish Gamemodes & Roles

Polish Gamemodes:

Polish Roles:

Expand Lobbies, Menus, Settings

0.3 - Alpha: More Systems

Now adding less core but still crucial systems, and expanding previous systems.

Basic Atmospherics

Basic Electricity

More Health & Combat

More Health:

It doesn't need to be 100% fool-proof because we are very early in development and the UIs will be reworked in depth in the future to look nicer and be consistent.

Port Remaining Secondary Systems. None of these will be a "piece of cake" but they shouldn't be rocket science either. The systems are already made, they just need to be ported over and any new issues resolved.

Add basic SFX & anims:

Fixes for the Rework major milestone.

GitHub Projects page
Releases
0.0.1 - Server & Lobby
0.0.2 - Management & Documentation
0.0.3 - Round System
0.0.4 - Simple Character Controlling
0.0.5 - Port Interactions System
0.0.6 - Port Tilemaps
0.0.7 - Fixing, Cleaning, Testing
0.0.8 - Character Rig & Animation
0.0.9 - Basic UI Guidelines & Rework
0.1.0 - Finalize Rework
🛣️
Page cover image