Repository navigation
Chrome Dino: Chrome's dinosaur game in NumPlay - #66
Merged
Merged
Conversation
The game now follows Chromium's dino_game (BSD license, see LICENSE), as Chrome plays it on a screen 320 pixels wide, at Chrome's 60 frames a second: a start at speed 3.84, 0.001 faster each frame up to 13; a jump as high as the key is held, ducking, and the quick drop in the air; small and large cacti, alone or in groups once fast enough; pterodactyls from speed 8.5 at Chrome's three heights (jumped, ducked under, or flying over); Chrome's collision boxes; the score flashing at every 100; night every 700 points for 12 seconds, with the moon's phases and the stars; and Chrome's GAME OVER with its restart button. The pictures are Chrome's sprite sheet, packed by tools/sprites.py (5.5 KB). On the calculator, OK or Up jumps, Down ducks, Back pauses (Resume, Restart, Quit game, which asks first), EXE plays again at once after a crash and Home quits; the keys are written under the game. The best score is saved, and the first version's file is read too. tests/test_dino.c checks Chrome's numbers, the keys and the drawing, then plays long games under the sanitizers.
…e, Upsilon Chrome Dino comes after Tetris in the launcher, and the other games keep their screenshots as they were: NumPlay has room for it. It gets its README, a how-to-play section, a thumbnail and a gallery GIF, and the launcher GIF is recorded again. The README's grid, credits (LilyTheCatgirl, Chromium) and count (19 games) are updated. Its texts and card come in French and Chinese, and it is in NumPlay-Upsilon.nwa (15 games). test_games.py and test_upsilon.py play it, and its icon has the other apps' corners.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Chrome's dinosaur game for the NumWorks calculator: inside NumPlay, after Tetris, and on its own as
ChromeDino.nwa. First brought to NumPlay by @LilyTheCuteCatgirl, from her version for the calculator's Python.The game
games/dinorun/LICENSE), as Chrome plays it on a screen 320 pixels wide, at Chrome's 60 frames a second:tools/sprites.pypacks them into 5.5 KB.Changes from the first version
In NumPlay
NumPlay-Upsilon.nwa(15 games).NumPlay.nwainstalls with about 25 KB to spare, andChromeDino.nwais about 21 KB.Tested
make nwa apps checkandmake lang: every app and language build fits the calculator's flash and RAM.tests/test_games.py, standalone and in NumPlay (Home and On/Off quit, RAM cleared, the save written and updated). Alsotest_upsilon.py,test_small_ram.py,test_uninstall.pyandtest_progress.py.make -C games/dinorun host-testchecks Chrome's numbers (the jump, the speed, the obstacles' rules, the collision boxes, night, the score's flashes), the keys and pause menu, and that sending only changed tiles leaves the screen identical to a full redraw. It then plays long games under the address and undefined-behaviour sanitizers.