Post AcuN3yHOaROB0P6LVA by kalak451@freeradical.zone
 (DIR) More posts by kalak451@freeradical.zone
 (DIR) Post #AcuMqxdpeEpZGIOMvw by kalak451@freeradical.zone
       2023-12-17T17:20:06Z
       
       0 likes, 0 repeats
       
       I've completed "Clumsy Crucible" - Day 17 - Advent of Code 2023 #AdventOfCode https://adventofcode.com/2023/day/17Fought with this a lot this morning.   Had a general solution up in a few min.  But fought with how to apply moves.   Ended up having to index costs by both direction and position, still not entirely sure why, but it worked
       
 (DIR) Post #AcuMqyevrdIyPzulHs by tek@freeradical.zone
       2023-12-17T18:02:28Z
       
       0 likes, 0 repeats
       
       @kalak451 Same here. That was tough. The cost depends on which direction you're coming from, which might not be optimal because of the distance constraint.
       
 (DIR) Post #AcuN3yHOaROB0P6LVA by kalak451@freeradical.zone
       2023-12-17T18:04:34Z
       
       0 likes, 0 repeats
       
       @tek Yeah,  I noticed I was getting a different answer depending on which way I sorted my priority que.  So I figured it was a direction thing.   Of course the original version only gave me the correct answer if I had the queue sorted wrong and the full data set wouldn't finish.
       
 (DIR) Post #AcuNaHHJUATFCBT3xY by tek@freeradical.zone
       2023-12-17T18:10:42Z
       
       0 likes, 0 repeats
       
       @kalak451 Ugh. Are you me?