Quartz 4

Daily Notes

5 min read

📅 Daily Notes - 2025-12-14

💭 Quick Thoughts

In terms of organising the vault, a few changes need to be made:

  1. Projects
  2. Segments

I might need to actually work with a model to come up with a better strategy. But the basic point is that we need to separate tasks into sprints or stories and then have dedicated times or versions for projects, rather than leaving everything open-ended.

We also need a new project for the Godot-Mars project.

I’m going to export everything from Jira and then say that star-sailors is closed for V2 and then we could have a new area for v2 patches or something.

Also, now that I’ve fixed the fountain pens, I’ll need to define the legend properly.

And there needs to be a way to archive the daily notes

🗣️ Meetings & Conversations

💡 Ideas & Brainstorming

Physical-notes should separate media files and the content. I need to compare GPT’s “understanding”/transcriptions with copilot (sonnet-4.5) It turns out that sonnet-4.5 sucks.

When it comes to the segments or versions, I need to create folders inside each project for segments, and I should probably manually define the folders for project components/concepts.

Here are the current segments, in my view:

  • Star Sailors
  • Bumble
    • Demo
    • Release
    • Coral/Fish extras
  • “Geodrink”
    • Demo
    • Release
  • Godot-Mars
    • Setup
    • Integration into SS ecosystem
    • Mission introductions
  • Roving
    • Demo - not in play for now. A note on Roving - I think I’m going to do it in Godot. Now that we’ve got the godot-rn integration working, it just makes sense. Provided that I can come up with a working version that experiences the same great timing/latency values that the base godot-rn framework provides, it just makes my life easier, rather than trying to shoehorn everything into a typescript application.

When it comes to the setup for godot-mars project, here’s what I’m thinking is remaining:

  1. Inventory
  2. Farming/crop growing
  3. Save state - either local or with supabase (this goes beyond the scope of the initial template)
  4. Enemies/NPCs
  5. Day/date transition
  6. Placing items/blocks
  7. Resources
  8. Level building

For Star Sailors, I’m thinking that I’ll have two segments running (for now) simultaneously - Product Hunt launch, and the patches version. Scope is defined as:

  1. PHL → everything required to get Star Sailors up to scratch for a strong showing on Product Hunt
  2. Patches → bug fixes, UI improvements & mechanic adjustments (e.g. Notifications , better drop rates, more documentation/instructions, etc) After PHL, I’ll know more about what people like and dislike about the current version, and I’ll say that V3 is about implementing immediate feedback and rebuilding the missions/storyline around projects that the users want to participate in. I’m not sure when I want to resume full-time work on the web version and I also don’t want to have the web version interfere with the work on the newer projects.

Here’s how I think I’ll organise project documentation:

  • Star Sailors (web):
    • Missions
    • Components
    • Instructions/UI
    • Analytics
  • Godot-Mars:
    • Terrain
      • Terrain generation
      • Manual levels
    • Backend
      • Saving data
      • Generating content
      • Populating content
      • React Native
    • Inventory
      • Item dictionaries/lists
      • Item ideas
      • Storage
      • Research
    • Missions
      • Mission lists/ideas
      • Citizen science projects
    • Scenes
      • Mining
  • Bumble:
    • Backend
    • Bees
      • Hives
      • Pollination
    • Plots
      • Expansions
      • Terrain
      • Farming
      • Weather

I think it’s time that I properly build the new website for scroobl.es:

Projects: Star Sailors ecosystem -

  1. Star Sailors client
  2. Bumble - coming soon
  3. “Voxel” - coming soon Decentralised technology -
  4. DeSci Nodes citizen science community plugin (partnership)
  5. ChopDot.xyz (collaboration)
  6. ScopeSettings

This way, there is a clear indication of the current projects.

Godot-RN template will/should consists of:

  1. Supabase integration
  2. Supabase login that pushes to the godot client
  3. Godot inside RN app (obviously)
  4. The ability to write back from actions inside Godot to RN + Rn-backend
  5. View discoveries - common link between all games in the Star Sailors ecosystem

When it comes to the projects I want to integrate next into the ecosystem, I think it’s more relevant to discuss in terms of mechanics I want to see -

  1. Construction
  2. Fishing #AreWeAlone is something I’ve been discussing for ages. Possibly, building a standalone minigame around that.

Roving would just be controlling a rover, finding resources and selling them, or refining them and selling them. Possibly later I could integrate a satellite mechanic for finding dust storm residue or spiders, maybe cloud harvesting. However, I’m not sure if that would be too complex in the early game and I also need to keep the graphics in mind. When it comes to graphics for the Roving game, I can probably just grab the 3D templates for Mars (maybe multiple, as long as they have the same texture parameters) and just create different scenes. If I make the rover body small enough, I can do a lot with the limited space of the accessible online terrain templates. And then, if I decide to continue it, I would probably have the capacity to build a terrain generator at that point.

One idea is that there’s an app for all the games, because, as seen in the current version of godot-rn template, we can fit multiple godot builds into one RN app. However, it would likely cause confusion for users who are focused on one mechanic/app. Possibly deeplinks would be a better strategy.

Generating terrain - Based on current classifications, I think I can create pixel art templates for different landscape/structure types, and rules - e.g.

This way, content from the classifications can fill in the terrain and the maps of the surface.

After defining the stories for everything, and setting up the Product Hunt launch requirements, I’m going to prioritise finishing the Godot build, website for https://scroobl.es, and then organising the stories/tasks per day. Creating a marketing strategy or at least templates for social posts with GPT could be a step.

✅ Tasks

  • [ ]

Archived from Daily Dashboard on 2025-12-14

Graph View