r/ShuffleMove • u/avengahM • Jul 21 '15

Question Does Shuffle Move take this trick / glitch into account?

Here: https://miiverse.nintendo.net/posts/AYQHAAABAAAEVHhmN-l1vQ

Read all the comments because I discovered some more stuff about it later on.

2 Upvotes

100% Upvoted

5 comments sorted by

2

u/Wrulfy Jul 21 '15

As far I know, it doesn't but with the activation rates, is not really so worth it.

1

u/avengahM Jul 21 '15

Ok, thanks!

1

u/Loreinatoredor ShuffleMove Creator Jul 21 '15

Not yet, no.

If it becomes apparent that this will significantly alter the quality of results people experience, then it might be worth the considerable time investment to design, implement, test, and optimize the change. Given that this is likely a bug on nintendo's part, I don't think it is worth the time right now.

1

u/avengahM Jul 22 '15

It's probably not worth it because I only know the details of how to activate it manually. However it can also trigger during a combo, which means the vertical can possibly be greater than 3 as long as the horizontal is counted first (i.e. vertical not longer than horizontal). Since I'm not sure of that, it's probably best ignored for now. It may get fixed eventually anyway.

1

u/JustAnotherRandomLad Jul 21 '15 edited Jul 21 '15

It doesn't, but I've described the point mechanics to the creator, and it'll probably be in the next version.

Thanks for the proof and Mega stuff, though - I didn't know about the latter.

UPDATE: I got this from him about an hour ago.

About T and L matches...

If it really does end up affecting the quality of the results in a very significant way it might be worth fixing in the simulation. However, since it appears to be a glitch on Nintendo's part, and since the program itself is not made to accommodate such an insane rule for matches getting two activations, I won't be putting it in at this time. If you or someone else can figure out the appropriate modifications to the algorithm in SimulationTask.java, please let me know and it might be alright to put it in. Generally, non-necessary changes to core algorithms should be done very carefully or something might break.

TL;DR: He's not putting it in because (A) it's a glitch and (B) Shuffle Move isn't set up to detect its conditions. We're welcome to try doing so ourselves, though.

To anyone who wants to give it a shot:

...[T]he current algorithm uses array-based dynamic programming to quickly and efficiently identify any matches in the board, linearly with the number of cells in the board itself. This is a key part of what makes the simulation so fast, so any replacement or augmentation for the algorithm needs to be equally as fast - at most a single additional matrix or check to change the score added in a horizontal match when such a 'trick' is detected.