#Puztrix Playdate

18 messages · Page 1 of 1 (latest)

onyx mason
#

Puztrix is a remake of the Gravnic game from inside the NES Puzznic game.

Game Features:

  • 80 levels of the original game
  • Level editor to create your own levels and level packs
  • High score saving and submitting for the original levels

Controls

  • Dpad/joystick: Select menu's and options. Choose a direction for all blocks to move in game mode. Move selector in level editor
  • A: Confirm in menu's, placing or erasing a block in level editor, give up level in game
  • B: Back in menus and game (to title screen)
  • X: Reboot game & select next source pictures (1bit, colors 1, colors 2 (nes))
  • L1: Hold to select previous piece while editing a level
  • R1: Hold to select next piece while editing a level

Instructions:
Game is ready to run

Tested on:
(X) [480 x 320] (RG351P)
(X) [640x480] (RG35XX Plus, RG351V)
(X) [720x720] (RGB30)
(X) [Higher Res] (X55, RG503)
(X) AmberELEC (RG351V, E6)
(X) JELOS (X55)
(X) ArkOS (RGB30, RG351P, 353VS, RG503)
(X) muOS (armhf) (RG35XX plus)

sturdy tundra
#

<@&1216123318122577972> 😄

quartz frigate
#

✅ RG351P/ArkOS (480x320)

obsidian galleon
#

Works and looks great across everything, so 353VS/OGA Arkos and ACE/JELOS

uneven vortex
#

Works great on AmberELEC, RG351V (640x480)

real aurora
#

works fine on AmberElec, E6 (854x480)

grim vine
#

Works full screen on RG503/ArkOS

onyx mason
#

updated main post with all info

sturdy tundra
#

looks ready to submit

onyx mason
#

shall i do the PR or do i wait on status change (from testing to ready to pr?) or wait on more tests

fading stratus
onyx mason
#

ok will do thanks was not aware i could change the tag myself

uneven vortex
#

There is no one going through threads and changing tags ^^

onyx mason
#

yes was not aware of that

uneven vortex
#

What I do is checking up on ports that are in testing and see whats up with them.

sturdy tundra
# onyx mason shall i do the PR or do i wait on status change (from testing to ready to pr?) o...

so the general idea is once your port is tested you can do a PR against the repo. We double check it was actually tested, checkover the code once more for any small issues like credit (not a problem in your case), make sure the scripts look okay and that the port.json file is all up the scratch then we accept it. We require that for a new port two crew members "okay" a port. if it is an update to a port we usually just require one person to sign off on it. 🙂

onyx mason
#

i see ok thanks