# Mr.Toad's Fifteen puzzle with timer (modified by stannic)

#### Gallifrey

##### Member
Please make a version with the opposite controls. I find it hard to control

#### Jaycee

##### Member
7-2 Relay 4:36.386 @ 5.608 TPS = wow
2:17.861, 1:17.762, 35.998, 18.074, 5.675, 1.016 = 4:36.386

Super lucky on the 6x6 and especially 5x5.

#### uvafan

##### Member
7-2 Relay 5:07.258 4.748 tps

2:20.278, 1:32.334, 50.247, 15.994, 7.308, 1.097 = 5:07.258

659, 446, 235, 81, 36, 2 = 1459

#### Jaycee

##### Member
16x16 PB by over 15 minutes

44:32.921

#### vcuber13

##### Member
(1:39.694), 1:28.821, 1:32.858, 1:24.019, 1:24.233, 1:27.255, 1:21.660, (1:14.847), 1:25.289, 1:17.439, 1:24.529, 1:20.747, 1:21.216

Best Ao5 1:20.905 (8) 676.333 (7)
Best Ao12 1:23.521 (2) 699.6 (2)
Solves: 13
Mean TPS: 8.285

could you make a control scheme where
h left
n right
c up
t down

#### vcuber13

##### Member
its basically the right handed dvorak WASD

#### emolover

##### Member
47:01.302 16x16 solve.

Never again...

#### uvafan

##### Member
7-2 relay sub5

2:29.572, 1:19.399, 45.608, 16.019, 6.700, 1.059 = 4:58.357

679, 364, 205, 85, 29, 6 = 1368

4.585 tps

#### ben1996123

##### Banned
could you make a control scheme where
h left
n right
c up
t down
open the code in notepad or something and find the part that says function keyHander(e), use this to find the key code of whatever key you want and change the numbers.

if you want more than 1 key to do the same move, change it to this
Code:
if (keyCode == somenumber || keyCode == someothernumber)

#### vcuber13

##### Member
i know the syntax, but i would need to change it each time an update is done

#### ben1996123

##### Banned
i know the syntax, but i would need to change it each time an update is done
you could just make the function once and then copy and paste it instead of remaking it, thats what I've done with my control scheme.

also, this is obviously the type of thing I would make a haxprogram for. so I did, with the help of stannics awesome sliding puzzle solver.

Last edited by a moderator:

#### stannic

##### Member
I was using the arrows originally (and when I did a 255 puzzle solve earlier), but I'm much more used to using qcube, so I changed the controls.

I'm using j and l as left, f and s as right, i as up and k as down.
could you make a control scheme where
h left
n right
c up
t down

Please check if the controls schemes match your schemes (not inverted).

Edit: offline version is uploaded.

- stannic

you could just make the function once and then copy and paste it instead of remaking it, thats what I've done with my control scheme.

also, this is obviously the type of thing I would make a haxprogram for. so I did, with the help of stannics awesome sliding puzzle solver.

What.

What???

Edit:

7x7 mo10 sub2
pb 1:57.823 (previous pb 2:09.241)

times: 1:55.272, 2:04.647, 2:00.656, 1:58.717, 1:56.076, 2:03.074, 1:57.505, (2:07.420), (1:44.948), 1:49.919
moves: (666), 735, 710, 717, 710, 725, 747, (794), 687, 733
mean tps: 6.131

2:07.420 solve would be sub 2 if I had not swapped tiles 18 and 19. Spent ~10 sec to find and fix the error.

Last edited:

#### Carrot

##### Member
What is this... I am like 10 seconds IRL, but over 1 minute on the simulator

#### stannic

##### Member
v5.2 upd 6:

- Average in relay mode

- Fixed small bug with the timer (the time was showing only after second move of the solve). The bug was not critical, though (that is, the times were correct).

- Hiding some unimplemented (yet) features in relay mode

- Two more relay modes: Relay (w--) and Relay (h--). Old relay mode is Relay (w--, h--).

w-- denotes that the width of the puzzle changes during relay.
h-- denotes that during relay, the height of the puzzle changes.

So, for example, use:

(w--, h--) to relay puzzles 7x7 to 2x2
(w--) to relay puzzles 7x7 to 2x7
(h--) to relay puzzles 7x7 to 7x2

What is this...
This is speedslidin.

Last edited:

#### stannic

##### Member
7x7-2x2 relay sub 4
times: 1:52.047, 1:08.943, 27.016, 17.013, 7.086, 2.121 = 3:54.226
moves: 708, 429, 164, 98, 41, 11 = 1451
mean tps: 6.195

Edit:

Well, 1^3+...+n^3 ~= (n^4)/4 = n^3 * n/4. So if the amount of time is roughly n^3 we can expect a 2x2-16x16 relay to take about 4 times as long as the 16x16 itself, i.e. a bit under 2 hours for me. Not sure if I want to put in that kind of time, but it's not tooooo crazy.
Just solved 13x13 in 17:03.422. Movecount is 5732, mean tps 5.601. If it was 13x13-2x2 relay, then looking at my current averages it would be ~1 hour.

14x14 and 15x15 will take in common 40-60 min, and I can solve 16x16 in ~35 min. Adding all the times gives ~ 2-2.5 hours which is rather close to your estimate. I may try this someday early in the morning.

Last edited:

#### Jaycee

##### Member
7x7-2x2 relay almost sub 4:30
2:19.803, 1:09.652, 41.329, 17.610, 5.472, 0.916 = 4:34.782
773, 349, 219, 107, 27, 2 = 1477
TPS : 5.375
Horrible movecount on the 7x7. On the relay before this I solved it in 2:22 with 706 moves :/ 6x6 was really good though.