¶ 🛠️ Game Status
GLITCHOUT is currently in active development.
Translation: things work, things break, things get fixed, and sometimes fixing one thing breaks three completely unrelated things. Game development™.
Before we unleash GLITCHOUT upon the general population, testing is planned in stages:
¶ 🔒 Private Playtest
A smaller group of players gets thrown into the machine first.
We'll use this phase to test:
- Core gameplay systems
- Stability and performance
- Balance
- Bugs and weird edge cases
- Whether something is actually fun or just sounded fun at 2 AM
- Focused player feedback
Expect bugs. Possibly impressive ones.
¶ 🌍 Public Playtest
Once the private playtest has done its duty, we plan to open GLITCHOUT to a much larger group of players.
This lets us test the game at a bigger scale, gather more feedback, and discover creative new ways players can destroy systems we thought were perfectly safe.
¶ 🚀 The Plan
Development → Private Playtest → Public Playtest → Wider Release
Development will continue during all of these phases.
That means features, balance, content, maps, interfaces, numbers, buttons, questionable design decisions, and basically anything else may change between versions.
So yes:
This wiki may occasionally lie to you.
Not intentionally. Probably.
¶ 💻 Platform Support
GLITCHOUT is being developed with multiple platforms in mind.
| Platform | Status |
|---|---|
| Windows | ✅ Supported |
| Linux | ✅ Supported |
| macOS | 🚧 Planned — waiting on access to Mac hardware for development and testing |
| Android | 🚧 Functional — the game works, but the mobile UI is still cooking |
| iOS | 🚧 Planned / In Development — mobile work plus Mac hardware required for building and testing |
¶ 🪟 Windows
Windows is currently a supported development target.
It works.
A suspiciously rare sentence in software development.
¶ 🐧 Linux
Linux is also currently supported.
Yes, Linux users. We remembered you.
You may now return to explaining why your distro is objectively superior to everyone else's.
¶ 🍎 macOS
We intend to support macOS.
Right now, the main obstacle is extremely sophisticated cutting-edge technology known as:
not having a Mac.
Proper macOS development, building, and testing requires access to suitable Apple hardware. Once we have that, we plan to make macOS support available as well.
So macOS isn't abandoned.
It's just standing outside waiting for somebody to bring the correct computer.
¶ 🤖 Android
GLITCHOUT already works on Android at a technical level.
The problem is the interface.
Right now, the UI is primarily designed for desktop screens, where players have luxurious inventions such as:
a mouse.
The dedicated mobile interface still needs work before Android is considered ready for general use.
Current status:
Game: functioning
Mobile UI: please do not look directly at it
¶ 📱 iOS
iOS is in roughly the same situation as Android regarding the mobile interface.
However, Apple adds a few additional adventures involving:
- Building
- Signing
- Testing
- Apple development tools
- And, once again, having a Mac
Once we have access to the required hardware, proper iOS development and testing can continue.
¶ 🧪 Playtesting
Want to help test GLITCHOUT and gain the prestigious honor of finding a bug before we do?
Excellent.
Our planned progression is:
¶ 🛠️ Development → 🔒 Private Playtest → 🌍 Public Playtest → 🚀 Wider Release
Information about:
- Playtest dates
- Who can participate
- How access works
- How to apply or join
- What platforms are included
- Any requirements
...will be announced when each phase is actually ready.
We don't want to announce a date six centuries early and then perform the traditional developer ritual of delaying it twelve times.
Check the following pages for updates:
[🚧 Playtest information coming soon]
¶ 🎓 Tutorial
Confused?
⚠️ Please note: GLITCHOUT is actively evolving. Platform availability, features, playtest plans, and development priorities may change as development continues.
In other words: nothing here is carved into stone. The stone is also probably still in development.