Lemmings Forums

Lix => Lix Levels => Topic started by: mobius on November 23, 2021, 11:01:57 PM

Title: Cornerstone, backroutes
Post by: mobius on November 23, 2021, 11:01:57 PM

I did just a quick search and didn't see any mention of the level cornerstone. I solved it pretty quickly and easily imho with builders left over. My solution is just a bit simpler than the solution from the proof archive, which also has builders leftover. Is this a backroute?? Level seems easy for it's place to me.

Title: Re: Cornerstone, backroutes
Post by: mobius on December 02, 2021, 11:44:54 PM

is this the appropriate place to post this??

regarding Cornerstone and my previous post; I discovered a simple way to fix that backroute (if it is a backroute);

Spoiler (click to show/hide)

Move the portion of the starting platform [that gets thicker, that is the highest part] and the entrance; farther to the right. This way there is less room to bash from the bomber's hole. This means you can't stall the lix as much as I do in my solution.

Title: Re: Cornerstone, backroutes
Post by: Simon on November 26, 2022, 11:33:01 PM

Your solution doesn't have builders left over, it has 3 bashers and 1 floater left over.:lix-grin: In total, it uses 3/3 imploders, 2/2 builders, 2/5 bashers and 0/1 floaters.

Today, I found exactly this backroute to Cornerstone myself. I can try to fix Cornerstone as you describe, but I don't know the intended route. Would you like to give it a shot yourself, and re-cover the new version with a solving replay?

I'll look at the intended route only when nobody else wants to fix it.

-- Simon

Title: Re: Cornerstone, backroutes
Post by: mobius on December 07, 2022, 10:56:26 PM

I assume then that all replays in the database are in fact intended? Just asking cause the replay is by Proxima and

Spoiler (click to show/hide)

still has skills left over. and tbh isn't super different from our solutions

Geoo hasn't commented yet.

If this is fine I can make the fix, yes.

Title: Re: Cornerstone, backroutes
Post by: Simon on December 07, 2022, 11:03:55 PM

No, replays in the database aren't all guaranteed to be intended routes. Some can be re-coverings after a physics change. Only after a while, we started caring to have at least one intended route when covering.

The replays aren't judged to be backroutes or intended. Judging replays, and writing this into the replay itself, is an important long-term idea.

But I think you can implement your fix. As long as it removes this most surprising shortcut, it improves Cornerstone.

-- Simon