Bought and played for a while, 83 attempts with 12 corrects and max 2 corrects in a row. It s a very difficult game without visual and sound to aid figuring out the exact rhythm, and the game seems very strict about how much you can be off.
Suggestions:
- have an option to add 4 constant interval tiks at the beginning to help setup the base rhythm
- hold down the small white dot to return to menu so you can see progress without exiting
- have a way to visualize a rhythm similar to the example or skip it (maybe two finger hold?) if you are stuck
- some rhythms feel to have slightly uneven tempo. Is the duration of the tick taken into consideration when generating the tempo?
- increase tolerance to slightly off taps, and gradually increase the number of ticks (not sure you already do this but right now it’s too hard win many times in a row)
- tik of the day mode. A long tick that challenges people who can win it in fewest trials
Thank you so much for buying the app! I am glad to know that you like it :)
Also thank you so so much for the in depth feedback! I get what you mean about the game being pretty hard starting out - I was trying to balance between too hard and too easy but it seems I landed a little bit on the harder side - which is something I can fix!
Your ideas about adding a constant interval to the start, holding the white dot to return to the menu (love this one!), and seeing progress without closing the app are great! I will definitely take everything you said into account for future updates!
The timing of the Tiks is intentionally off to make the game a bit harder and add variety. I think the main thing that impacts how hard it is should be the tolerance of how close ur taps have to be to the Tiks, which is something. I can change to make easier, at least till the user gets around 40-50 correct or something.
I love the Tik of the day mode idea and is something I had written too to implement later on. Seriously all your feedback is amazing, thanks so much!! :)
Interval tiks would add "noise" to a game that has very limited output. How would I know if those tiks are the interval or the pattern?
I don't think I've ever gotten two correct in a row, but the fun of the gameplay comes from slowly learning the rhythm over a few tries. It's not entirely unlike Celeste or Super Meat Boy, where you learn the level over multiple attempts.
I'm worried that I would trigger any sort of menu accidentally. Two fingers might work but if I'm walking or something and gripping the phone in weird ways...
I will say that while walking home this afternoon, there was one pattern I got stuck on. Every other pattern, I was able to get past after a reasonable number of tries, but this one just seemed impossible and I had to quit and re-open the app. So I agree there either needs to be some way to skip patterns, or the pattern generation needs to be tweaked to avoid super hard outliers.
Edit: Fwiw, my stats are: 116 total attempts, 20 correct, 2 max in a row.
Thanks for posting this - I understand everything you're saying as well and will definitely balance all the feedback I am getting when making changes in a future update. I want to preserve the aspect of the game where it takes a couple tries to get past a sequence, but not too many to the point that it is irritating.
Triggering the menu by accident is a valid concern as well.
I will try and think of creative ways to balance all of this and make the end experiance even better. I appreciate your feedback!
Many years ago I learned from some Japanese TV show that you can use centrifugal force to get the very last bit of toothpaste out of the tube even if you can’t squeeze out any more. Something similar to this: https://m.youtube.com/watch?v=u-4MKefJqbc
One of the best articles I have read for years. It's easy to underestimate how difficult it is to make things "just work" in the first trial. I really envy the author's ability to plan for known and unknown situations. Marvelous job!
We published this paper "TMO: Transparent Memory Offloading in Datacenters" last year which covers some Linux memory management mechanisms that may be quite useful for providing reasonable estimations to application memory usage.
We observed that the real memory footprint for applications depends on many factors: file access pattern, disk IO speed (especially if swap is enabled), ssd vs hdd, application latency sensitivity, etc. Instead of coming up with some overly complicated heuristic, we use the Linux kernel provided memory.pressure [0] metric via cgroup v2. It measures the amount of time spent waiting for memory (page fault etc). Then by slowly reclaiming memory from the application until its memory pressure hits some target (say 0.1%), we can claim that the steady state usage is the actual memory footprint.
This may not be useful for PC but could be very useful for data center to track memory regression, and also to harvest disk swap without concerning too much about the cliff effect when the host runs out of memory and suddenly kernel pushes everything to swap space.
Just curious - if the usage of acronym here a soft-euphemism?
(So that only those who knew or care to know gets it)
edit: Thanks for the clarifications. That helps.
I'm asking for 2 reasons:
1. Discussing "nukes" openly where I come from would raise some eyebrows.
2. I see acronyms used on HN frequently - sometimes ambiguously even considering the context.
I don't think so, people could just say "nukes" but there are plenty of nukes that aren't capable of hitting targets halfway around the world. ICBM seems like the fastest way of saying "nukes that can hit stuff really far away" while also making a distinction from sub launched and cruise missile launched nukes.
The payload on the missile doesn't need to be a nuclear weapon of any sort. The important thing about the ICBM is that being further away doesn't stop it. Nuclear weapons are the obvious choice because it's hard to imagine why you want to strike something so very far away, at such great expense, with conventional explosives.
The German V2 rocket from World War II has a maximum range of about 320km. So you literally can't fire one from say Berlin to London. They were actually launched from coastal sites in the Netherlands and other occupied countries, and as the Allies took territory after Overlord, the targets changed to cities nearer Germany because the launchers were pulled back.
The program collects system resource metrics into a data structure and we need to display the fields with different styles and formats. In order to decouple the data structure from rendering, Queriable (Keyable) and FieldId (combine KeyPath + mirror struct into enum) are used. I will definitely like to checkout the KeyPath implementation as it seems more general.
I was recently searching for wedding gift for my photographer friend and found this. There does not seem to exist many other e-paper art frames and this one looks decent. It also has some open source software (https://github.com/framelabs-eu), but the firmware seems closed-source.
Suggestions: - have an option to add 4 constant interval tiks at the beginning to help setup the base rhythm - hold down the small white dot to return to menu so you can see progress without exiting - have a way to visualize a rhythm similar to the example or skip it (maybe two finger hold?) if you are stuck - some rhythms feel to have slightly uneven tempo. Is the duration of the tick taken into consideration when generating the tempo?
Interesting game overall. Well done
reply