General Hints for solving levels

Started by Forestidia86, August 21, 2020, 02:23:02 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Forestidia86

I'm far from the best solver and the advice is tailored to my way of thinking but following some general hints/ways of thinking that helped me solve tricky levels:

Hint 1 (Problem focusing)
Think problem oriented: Think about what your main problem in a level is and what would solve it and if/how you can make it possible.
Hint 2 (Openness)
Try out things, even if they don't look as if they could work because it can give you a feeling of what can work and of what you have available.
Hint 3 (Rethinking)
If your attempts remain fruitless or a skill short etc., consider trying sth different or question your assumptions about the solution.
Hint 4 (Relevance of terrain design)
Look closely at the terrain design, if it tells you sth., e.g. how to use your skills.
Hint 5 (Skill management)
Think about what skills seem to be "locked in" and concentrate on how to work with the remaining open ones.
Hint 6 (Relevance of deliberate design)
Consider that a level is deliberately designed and trust that the design is in a way that things work out, even though timing can get tight at times.

Your mileage may vary on any of these ones but I thought it can be helpful to share them and bring them to discussion if there is inclination to.

Wibble

Those are all good hints for general problem solving - many are ideas I try to consider when stuck. Linked with skill management, I'd also add that working backwards can help - if you know you can solve a level by getting all lix to a particular place then the problem turns into "how do I get there" and is simplified.

The one I am worst at dealing with is spending ages pursuing a red herring path that almost but not quite works.






Forestidia86

Quote from: Wibble on August 21, 2020, 06:57:26 PM
The one I am worst at dealing with is spending ages pursuing a red herring path that almost but not quite works.

I know this problem, unfortunately even intended solutions can theoretically get tight on timing or skills. Sometimes I went full terrier on a solution path and found backroutes by squeezing the last bit out.