Earlier quoted context omitted.
You caching in memory or disk? Redis or db might survive the crashes and reduce future ones
on disk, so basically I'm trying to save the image of a solution and reuse it if the same quiz is required. So instead of recomputing the result just return the same image.
enclose.horse
81–90 of 242 posts
Re: enclose.horse
#82Re: enclose.horse
#83Re: enclose.horse
#84Earlier quoted context omitted.
on disk, so basically I'm trying to save the image of a solution and reuse it if the same quiz is required. So instead of recomputing the result just return the same image.
Got it. Is that cache surviving the crashes?
Re: enclose.horse
#85Great game, I love it! I hope the author is collecting juicy analytics. They would be useful if they ever want to bundle 100 levels in order of difficulty and release this as a Steam game (which I would absolutely buy!) I don’t think the gates should animate up into the air. It breaks the visual logic of 2D for no benefit. It’s subconsciously confusing to see a gate I place in one cell move to occupy pixels in the ce…
Re: enclose.horse
#86Earlier quoted context omitted.
Got it. Is that cache surviving the crashes?
I'd have to host it somewhere (s3?). Right now I only commit the solution png to github. OFC it's not a good option but it's free and fast.
Re: enclose.horse
#87Earlier quoted context omitted.
> I don’t think the gates should animate up into the air. I think it should go up, otherwise it doesn't look like a wall. It would look like something the horse can step on and run over. For the water it makes sense to be flat flat and that the horse doesn't want to touch it: it is water-shy.
To me the current design doesn't look like anything at all. I don't see a gate or a wall, just two rectangles.
Great game! Feature request: add a button that shows my submitted solution. I'd like to be able to compare it with the optimal solution (so it'd be nice if a single tap could toggle between my submission and the optimal).
Re: enclose.horse
#88I am curious on how you would algorithmically find the optimal solution for this kind of problem for much bigger grids. I wanted to do some seed finding in Factorio for the same exact problem using the generated map images, but never found a good solution that was fast enough.
Constraint programming seems to be a fitting approach. Input would be number of walls, and the location of lakes. The decision variables would be the positions of walls. In order to encode the horse being enclosed, additional variables for whether horse can reach a given square can be given. Finally, constraints for reachability and that edges cannot be reached should ensure correctness.
See
https://gist.github.com/Macuyiko/86299dc120478fdff529cab386f...
Re: enclose.horse
#89Earlier quoted context omitted.
I disagree about the replayability aspect. It‘s a daily challenge, so come back tomorrow. I quite like it.
I seriously don't get the idea behind daily challenges unless you want to keep users hooked to extract some value from them, but that doesn't seem to be the case here, as there are no ads. Just show all the different levels at once.
Re: enclose.horse
#90Earlier quoted context omitted.
To me the current design doesn't look like anything at all. I don't see a gate or a wall, just two rectangles.
+1 to this. It's also visually confusing, the gate looks like it's covering two cells. Great game! Feature request: add a button that shows my submitted solution. I'd like to be able to compare it with the optimal solution (so it'd be nice if a single tap could toggle between my submission and the optimal).