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...
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...