The only downside is theres multiple ways to reach the same outcome, and unless you program it exactly what you're looking for it gives a false negative that the solution isn't correct
That's not really true. For the actual exercises where you need to solve a problem yourself, the system only tests that the code produces the correct output. It doesn't require you to use a specific approach, so there are infinite possibilities, although it may forbid certain approaches that go against what the current section is trying to teach.
There are many steps that do require entering exact code, but that's because in those cases the code itself is the whole point, not just the output. In most cases they're in places where new concepts are being introduced, so jumping to exercises wouldn't make sense. Often you're even being asked to enter code that does something 'wrong' so you can see common mistakes in action.
Steps that require exact code are always explicitly labeled as such under the 'Requirements'. In most cases the code that needs to entered is given exactly in the text in one piece. When it isn't, the Requirements will always contain extra clarification for the instructions. And if that isn't enough, it's still always possible to look at the solution, although for that kind of step it shouldn't typically be needed.
Your comment sounds very similar to the most common kind of feedback I used to get from users who found the instructions unclear and got stuck. I recently made a major update to the user interface to solve this problem, including the stuff in the paragraph above. If you've used futurecoder before it's possible you haven't experienced this yourself. If you can't see it right now, you may have old content cached, hard refresh the page in your browser. Also, the new features haven't been translated yet so they're only available on the English site.
