Skip to main content

Posts

AbyssalBits — Polish you verify in the game

NgDinhNha · DEVLOG AbyssalBits — Polish you verify in the game Margins, backgrounds, labels and floating text. A round of small player-facing fixes, and a reminder to look at the running game instead of trusting the code. View on Google Play English Tiếng Việt 日本語 English What happened during a round of player-facing polish AbyssalBits is a pixel-art dark-fantasy action RPG and procedural dungeon crawler for Android. This is what happened during a round of player-facing polish. The HUD and the first screens The four menu buttons in the top-right of the HUD sat too close to the screen edge. They moved inward, and the avatar on the left got the same outer margin from one shared value, so the two sides cannot drift apart. The safe-area protection for notched screens stayed on top of that. Gameplay and Town share the same HUD code, so both picked up the change. Loading and the...
Recent posts

AbyssalBits — Release checks and two Pythons

NgDinhNha · DEVLOG AbyssalBits — Release checks and two Pythons Getting the 1.1.0 release candidate out meant failing asset checks, two different Python setups and a toolchain upgrade. The fix gave the build its own Python environment instead of trusting whichever one the path finds first. View on Google Play English Tiếng Việt 日本語 English What happened while getting the 1.1.0 release candidate out AbyssalBits is a pixel-art dark-fantasy action RPG and procedural dungeon crawler for Android. This is what happened while getting the 1.1.0 release candidate out. The candidate and its gates Version 1.1.0 began as a release candidate: bump the version, then run every release gate the project already had, from smoke checks and asset verification to unit tests, compilation and lint. Three earlier findings in the display-text check were fixed instead of exempted, and the build wrapper...

AbyssalBits — Preparing A Release Around Four Play Recommendations

NgDinhNha · DEVLOG AbyssalBits — Preparing A Release Around Four Play Recommendations Google Play Console sent four recommendations on the 1.1.0 release. I could have waved them off as noise. Instead I prepared the 1.1.1 release around them. View on Google Play English Tiếng Việt 日本語 English What happened when I prepared a release around four Play recommendations AbyssalBits is a pixel-art dark-fantasy action RPG and procedural dungeon crawler for Android. This is what happened when I prepared the 1.1.1 release around four Play recommendations. Four recommendations, one maintenance release Google Play Console listed four recommendations on the 1.1.0 production release: edge-to-edge display might not work for all users, a deprecated display-cutout mode, a large-screen resizability and orientation item, and a bitmap downsampling item. Version 1.1.1 was planned as a small maintenanc...

AbyssalBits — Gates that checked the wrong file

NgDinhNha · DEVLOG AbyssalBits — Gates that checked the wrong file The privacy policy moved, the old draft was deleted, and the release gates kept reading the draft. Fixing that meant rebuilding the policy and pointing every check at the file we really ship. View on Google Play English Tiếng Việt 日本語 English What happened when the release checks read the wrong privacy policy AbyssalBits is a pixel-art dark-fantasy action RPG and procedural dungeon crawler for Android. This is what happened when the release checks read the wrong privacy policy. Gates pointed at a file that was gone The privacy policy had been moved to a new location and the old draft deleted. But the release smoke check, the Gradle inputs of several release tasks and the Python validators behind them still read the deleted draft, so a full release bundle failed. Worse, one validator required the policy to mention ...

AbyssalBits — Garbage Created Every Frame

NgDinhNha · DEVLOG AbyssalBits — Garbage Created Every Frame Small objects, created and thrown away on every frame. In a game loop, that repeats for as long as the loop runs. View on Google Play English Tiếng Việt 日本語 English What happened when the game loop kept making garbage AbyssalBits is a pixel-art dark-fantasy action RPG and procedural dungeon crawler for Android. This is what happened when its render paths created new objects on every frame. Small objects, every frame After the sprite lookup work, a review of the gameplay draw and update code found clear, low-risk allocations that happened on every frame. Most were colors: a new color for a mini-boss shadow, a biome wash, the low-HP vignette or the ultimate flash. The telegraph system created a new color on each call, dozens per indicator per frame. Some paths built a fresh list each frame, and HUD labels were rebuilt as ...