Asteroids Development Post - Bit Crash
{Week 6}
Game Preview
This week in Bit Crash, I focused on transforming the basic enemy mechanic into something more intentional and reactive. Not just floating obstacles, but rogue data fragments that hunt you down after vanishing into the void. Alongside this, I implemented the game’s scoring system tied to asteroid destruction, officially kicking off the arcade loop.
Enemy System: Immovable Hazards That Return I created a set of immovable hazards (DataFragments) that drift across the screen and damage the player on contact. But instead of deleting them when they exit the screen, I wanted to reinforce the glitch-core theme, so now they disappear, wait between 3 to 6 seconds, and then respawn from a random screen edge, launching directly toward the player’s position.
This gave the game a more sinister rhythm, and the unpredictability of where they’ll come from adds tension. I even added spinning to each fragment as they drift, making them feel more like destabilized chunks of corrupted memory.
This system taught me a lot about using object variables to manage internal state (such as ShouldRespawn and RespawnTimer) and reinforced how small, modular logic chunks can build emergent behavior.
Player Movement and Bullet Feedback I also made big improvements to the player movement system this week. The player now rotates toward the mouse cursor and fires with the left mouse button. To add more weight and feedback to firing, I added a slight knockback that pushes the player backwards when shooting.
This gave shooting a much more satisfying feel. It not only helps sell the impact of the bullet visually, but also introduces a skill-based mechanic where players can tactically reposition using their own firepower. It fits perfectly into the glitchy aesthetic and adds some interesting risk to spamming shots.
Point Scoring: Asteroids Asteroids are currently the only source of score in the game. Destroying one adds 1 point to a global score variable, which is displayed in real-time using a UI text object. The destruction is paired with feedback like screen shake, visual effects, and sound cues to reinforce the moment.
Eventually, score will tie into leaderboards, unlockables, and Endless Mode, but for now, this system helped me lock in the core arcade loop: aim, destroy, reward.
This was the first real implementation of the reward loop. Fullerton talks about creating clear, compelling outcomes for player actions, and this felt like the first time that started happening naturally in my game.
Done This Week:
Main menu with ambient glitch-core soundtrack
Player movement and bullet recoil system
DataFragments now respawn with delay and track the player
Asteroids can be destroyed for score
Score system with UI feedback
Visual and sound effects for damage and point gain
Random spawn system with directional targeting for enemies
This week was the most rewarding yet. The mechanics are starting to talk to each other. Enemy behavior is feeding into movement design, movement is influencing combat, and combat now ties directly into the scoring loop.
Let me know what you think! E: [email protected]
