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
91–100 of 242 posts
Re: enclose.horse
#92Re: enclose.horse
#93My algorithm, by hand, was as such:
1. Start with the smallest possible valid solution (1)
2. Expand slowly, and each "step" (like, moving a wall or two around to "obvious" spaces) must be a valid solution (this brings you to 40-60 score, depending on your choices, on day 8). Continue to step 3 once you can't see anything obvious.
3. Look at possible places where you could expand, but need 1 more block. You'll find one eventually.
4. See if you can spare any walls anywhere, using diagonals for example. If so, place the solution from 3 and go to 3 (repeat). If not, go to 5.
5. Count or estimate the squares gained by doing your improvement from 3. See if you can reduce your score by less than that, pessimizing your solution, to gain 1 wall. Once you've found one, go to 3.
That got me to the optimal score within 15 mins or so.
Re: enclose.horse
#94I think you should change the cherries to a battery and call the game Correct Horse Battery Stable.
Reference[1] for anyone wondering.
Re: enclose.horse
#95Great 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…
I hope they're not. Can't we have a few things in this world that are just fun without going and sticking surveillance on them?
Re: enclose.horse
#96I think you should change the cherries to a battery and call the game Correct Horse Battery Stable.
Re: enclose.horse
#97Great 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…
> I hope the author is collecting juicy analytics. I hope they're not. Can't we have a few things in this world that are just fun without going and sticking surveillance on them?
Re: enclose.horse
#98Score init should say N/EIGH instead of N/A, otherwise great.
Re: enclose.horse
#99Great 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…
> I hope the author is collecting juicy analytics. I hope they're not. Can't we have a few things in this world that are just fun without going and sticking surveillance on them?
Please, show me a piece of software, or game, that is perfect the first time it is made.
Re: enclose.horse
#100lovely, I've created a solution finder for it. 1. Do a screenshot of the grid (try to include walls as well) 2. Open https://enclosure-horse-solution.onrender.com/ 3. Make sure the number of walls are correct in the input (bottom left) 4. Press "Solve" PS: It might crash as it's on the free version of render. I've added a caching layer. Here's the github so you can run it locally: https://github.com/langarus/enclosur…