🌌 ↝ Star Sailors V2.1 Prerelease - Onboarding Chapter
Pre-release
What's Changed
- 🚥🫥 ↝ [SGV2-140]: Clean up old mission groups by @Gizmotronn in #121
- 🚦🌆 ↝ Revert "🚥🫥 ↝ [SGV2-140]: Clean up old mission groups" by @Gizmotronn in #122
- 👾🦦 ↝ [GP-56 SGV2-142]: Creating onboarding components, schema & plan by @Gizmotronn in #125
#StarSailors Pre-Release 2.1 is out, with a revamped onboarding system 🌌
Take home a planet that you discover, and make it your own with unique classifications & achievements.
Chapter 1 begins development this week
Full Changelog: Prerelease-aussieterrier...prerelease-athene-cunicularia
Some notes:
Same as the current sprint - functional [set of …s] component to introduce the user to the new mechanics
The main aim of this chapter is to introduce the user to the key mechanics of the early chapters, including
https://signalk.atlassian.net/browse/SGV2-136?focusedCommentId=10569
We need the user to be introduced to the main mechanics over time, here's what I would say the full list of mechanics would be:
Getting resources
Using rovers to collect small amounts
Upgrading your roover/automaton to get more (variety & quantity)
Deploying dedicated mining stations/protocols ^5f21c1
Building
Creating structures [[#^5f21c1]] ^46498e
Creating base components (this is probably the most sandbox component overall, I'm just not really sure what the users could build. The goal would be building and customising your terrariums/post cards so what can we do there...)
A note that this is probably a way off because I don't think we have the infrastructure ready to integrate a dedicated game engine into the web build yet
Classifying data (which comes from structures) [[#^46498e]]
Planet data
Planet candidate validity - lightcurves (determining if the planet you're looking at is real)
Fill-in data (essentially data from Earth/solar system entities that we use to fill-in the missing pieces of the user's EXO-planet)
Martian cloud data
Mars rover photos - user works with these to "populate" (add content) to their planet (e.g. adding mineral deposits (which would also come from mining citizen science projects/modules later) or animals)
On-planet data
Animals
Classifying others' animals (users' submissions as well as dedicated research projects' assets)
Adding new animals to the database (file upload, can extend to pretty much anything). #zoodex component/module, this will serve as one of the big entry points for Capt'n Cosmos
Here's a brief list of what I would say our UI components would be (that we need to sort out for the onboarding chapter & chapter 1):
Dynamic background image, organisation of layout (structures, automatons, anomalies/other entities)
Dynamic planet images (for the terrarium/post-card)
![[2.png]]
See [[Planet list - Anomalies]]
Public dynamic routes to view anomalies (we also need to take a look at overhauling how "anomalies" are organised database-level to better support non-planet [candidate] entities) [[NWs S5 Week 4 & 5]]
Layout/vibe inspiration for Fred:
Voidpet
Hades' Star
Pixel Starships
Some other ideas (from pages like [[NWs S5 Week 4 & 5]]):
4. New narrative:
1. Starter planets
2. Base planet (location) sets for different mission paths
3. Build a bridge between the planet narrative/content and our content in the solar system (e.g. Martian clouds combining with the equilibrium temperature from the exoplanet)
4. A progression tree and map of your anomalies
Get a comprehensive planet & landscape generator based on user data, classifications & overall anomaly completion
2. Introduce a mechanic for post card features where users can see their discoveries, zoom in on a planet (so have dynamic routes based on the home page to see their setup on each anomaly) and their classifications
3. "Expeditions" or community events in the vein of No Man's Sky expeditions where there's an objective, a special reward, and some collaboration initiatives
We also need to get the user set up with a profile for their classifications (username/display name, avatar, bio/name, etc). How do we introduce Capt'n Cosmos in the onboarding?
So we need to take a look at the overall narrative and determine the order that users should be introduced to the different mechanics, e.g. what structures/data modules we put into the onboarding (e.g. the cloud classifying module will be introduced to the user in chapter 1/2, not in the onboarding (same with other, new structures)) and then sort out an Order of Operations (and subsequent long-term [responsive] layout) for this.
Sprint planning
Gp board
Goal: Components (generating, classifying & gameplay/mechanics) for onboarding (teaching users how to play the game, starting them off with a borderline starting point that feeds into the main game loop starting in chapter 1).
Zoodex/Animal classification (both uploading & "scanning"/classifiying [others']), Lightcurve classification, Rover photos. This will populate your first planet (chapter 1)
Update: Will review with @liquidnetwork.ai , I think we have a start of something. At the very least we can use this as a starting point for importing dynamic images with flask, which is probably the closest to my original design philosophy (see microservices I once came up with and abandoned 🙃 ).
I’m going to get onto putting the base images into the simple two-panel editor in https://signalk.atlassian.net/browse/SGV2-136 now as we don’t need to have a full dynamism yet, maybe we can convert lightkurve to a js package too (thanks Tim Meehan for the suggestion)
R2-D2/roover shaped terrarium
SGV2 board
Create a ticket to archive/keep track of components dir and relevant files (i.e. what will be retained and what has been functionally replaced as of now)
Goal:
Final nordkurve changes, including /terms route
Clone copernic repo, run supabase locally, make sure everything works, copy everything to a new page for nfts, update the table fields (new table schema on supabase) to be more in-line with spacibles/art NFTs, and then add a search component
Star Sailors - working simplified lightcurves for each of the basePlanets and integrate into the SGV2-14 workflow, give something back to the user
Idea -> standalone reading app, also good portal for researchers to add/view data (can be in game format or reading format)
