Planet900 -- Would this interactive pixel-art universe be feasible to build? #181229
Unanswered
bossshhh
asked this question in
Programming Help
Replies: 2 comments
This comment was marked as off-topic.
This comment was marked as off-topic.
-
|
Thanks for posting in the GitHub Community, @bossshhh! We're happy you're here. You are more likely to get a useful response if you are posting your question in the applicable category, the Discussions category is solely related to conversations around the GitHub product Discussions. This question should be in the |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Discussion Type
Product Feedback
Discussion Content
Hi everyone,
I’m working on the early concept for Planet900, an interactive pixel-art world inspired by projects like Floor796 — but focused on mythological realms, evolving timelines, and layered storytelling.
Right now, Planet900 exists mostly as worldbuilding and system design. Before I lock the technical direction, I’d love to get feedback from developers and artists on the feasibility and engineering challenges.
Core Concept:
Planet900 is structured as a multi-realm “stack,” where each realm has its own aesthetics, physics, and mythological influences (Norse, Greek, primordial concepts, etc.). Users explore by scrolling or navigating through interconnected animated scenes.
What I’m exploring technically:
Pixel-art animation pipeline (initially Aseprite → later a custom editor)
Raster assets (PNG/sprite-based)
Potential formats for smooth playback (sprite sheets vs. WebM vs. custom encoding)
Optimization concerns for a large animated site
Syncing multiple animated segments on a page
Whether this should be a web-native engine (Canvas/WebGL) or a hybrid approach
What I’d love feedback on:
What would be the smartest foundation for a project like this?
How would you approach playback/synchronization of many animated scenes?
Which technologies or patterns would help me avoid performance pitfalls early?
If you’ve built animation-heavy web experiences, what do you wish you knew sooner?
If the prototype engine proves solid, I’m planning to invite pixel artists/animators to collaborate — any advice for managing that workflow?
I'm not recruiting yet — just exploring the technical reality and potential of the idea.
Any thoughts, warnings, or suggestions are appreciated.
Thank you!
Beta Was this translation helpful? Give feedback.
All reactions