left/right = move
z = pull down
x = push up
Pull down dice and convert/clear them by pushing them up again. Much like Money Idol Exchanger.
2 x 2 = 3
3 x 3 = 4
4 x 5 = 5
5 x 5 = 6
6 x 6 = clear
2 x 1 = clear all connected
General game progression, chain conversion, color matching, etc. Some early music testing (disabled). Runs at 60 fps in native mode.
Better HUD, scoreboard, more music/sfx, specific game progression (goals, challenges etc). More things as I come up with them.
Yep, it's too easy at this point, but currently I'm mostly figuring out the mechanics. Working iteratively, I'm planning to add more variation and (difficulty) progression as I go.
About the star field, I've tried both, and while a black/white color palette gives a clearer distinction between what's what, the current palette blends more nicely with the rest. Not sure what I'll end up using at this point.
Yeah, I'd like to do something like that. Right now it's mostly about matching and scoring (you add to the multiplier by chaining). Suggestions?
Thought it'd be nice to see the progress, but maybe most people go for the last one anyway. :b
I personally think seeing the progress in the old carts is nice.
- Make UP and DOWN cycle the current color as well.
- Make LEFT and RIGHT repeat if you hold for a bit.
While you can use btnp() for repeats, I found that it takes too long for it to repeat for my tastes. Here's a little snippet base on a Tetris game I'm working on. Play the game and move the pieces around to feel this code in action. It attempts to make it easy to "tap" the buttons to move precisely but also makes moving a further distance fast. This code isn't optimized, sorry.
btn_debounce = 4 last_btn_t = 0 function _update() if btn(0) or btn(1) then -- initial button press immediately handled. later, btn_debounce must be met if last_btn_t == 0 or last_btn_t >= btn_debounce then if (btn(0)) -- handle left if (btn(1)) -- handle right -- subsequent button repeats come a little faster if (last_btn_t > 0) last_btn_t = 1 end last_btn_t += 1 else last_btn_t = 0 end end
Thanks, and thanks for the suggestions! I went ahead and implemented both, so they'll show up in next update. :)
There's quite a lot that isn't optimized in my own code, so I don't mind. :) However, I'm already using a another lib for keyboard, and it has a similar "pulse" behavior: https://www.lexaloffle.com/bbs/?pid=21816#p21813
[Please log in to post a comment]