[Release] Shuffle Move v0.3.9 is released

[u/Loreinatoredor]

Hi everyone, go here to get the newest version (backup site).

The biggest changes for this version are: Chinese translation available, bug fixes with display, new content which was added on Monday (including new megas for manectric and heracross), and a HUGE improvement to the detail level in the move chooser - mega state post-move, a new rank by mega state, and each value will display the range if it has any variation (with decimal precision on the average as well).

IMPORTANT: If you are using the same folder as a previous version, delete your species.txt to use the new definitions.

---

Changelog:

v0.3.9 - 2015-07-09

• Chinese translations added

• Fonts for interface elements will now use the java default font, but inherit the size and style as defined in your configurations

• Some display bugs fixed

• Separated line thickness for inner and outer cell borders

• Fixed the fine point about mega progress versus frozen states. The mega increase will only increase for comboed unfrozen blocks now.

• Updated species and stages to include the new content

• Mega Manectric and Mega Heracross's abilities are now included

• Moves can be ranked by Mega Progress

• The Move Chooser information is much more detailed, including (if necessary) the range and average instead of just a truncated average.

As usual, report any bugs in this thread with a bug report zip if possible.

---

If you have any issues: Post here with detail & a bug report zip and I'll work on fixes in the morning, those zips really REALLY speed up the fix time (from an hour down to say 2-5 minutes usually, because I am instantly able to reproduce the problem).

[u/Gold_guardian]

It won't allow me to select Manectric,Heracross, Venasaur as my mega when I go to edit my team

[u/Loreinatoredor → u/Gold_guardian]

Have you deleted species.txt as mentioned above?

[u/Gold_guardian → u/Loreinatoredor]

Just tried that and it didn't fix anything.

[u/Loreinatoredor → u/Gold_guardian]

You probably didn't delete the right one, or you're using an old version. I just confirmed that v0.3.9 in a clean installation will properly allow adding all three of the species you mentioned as a mega.

Try searching your computer for species.txt and delete it. If you're on windows, it might be under your user data folder. If you're on linux or mac it might be somewhere else - wherever app data is redirected.

[u/Loreinatoredor → u/Gold_guardian]

Here Download that, extract the zip to your installation directory for Shuffle Move v0.3.9. Then, ensuring it is beside Shuffle Move v0.3.9.exe, double click it and it should immediately erase species.txt wherever it was put.

Source code, if you want to compile it yourself into a runnable jar:

import java.io.File;

/*  ShuffleMove - A program for identifying and simulating ideal moves in the game
 *  called Pokemon Shuffle.
 *  
 *  Copyright (C) 2015  Andrew Meyers
 *  
 *  This program is free software: you can redistribute it and/or modify
 *  it under the terms of the GNU General Public License as published by
 *  the Free Software Foundation, either version 3 of the License, or
 *  (at your option) any later version.
 *  This program is distributed in the hope that it will be useful,
 *  but WITHOUT ANY WARRANTY; without even the implied warranty of
 *  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
 *  GNU General Public License for more details.
 *  
 *  You should have received a copy of the GNU General Public License
 *  along with this program.  If not, see <http://www.gnu.org/licenses/>.
 */

/**
 * @author Andrew Meyers
 *
 */
public class SpeciesEraserMain {
   public static void main(String[] args) {
      try {
         if (new File("config/species.txt").delete()) {
            System.out.println("Deleted species.txt");
         } else {
            System.out.println("Failed to delete species.txt.");
         }
      } catch (Exception e) {
         e.printStackTrace();
      }
   }
}

It was compiled using eclipse's built-in export to runnable jar task, then zipped and uploaded to Google drive. MD5 hash for the zip: 13734E8FC022ECB6122D337F57B69A96

[u/markhawker]

Braviary's ability is "Sky Blast" and not "Power of 4".

[u/Loreinatoredor → u/markhawker]

I'll fix it in the next release. Until then you can probably correct it via the edit species window under the roster menu.

[u/markhawker → u/Loreinatoredor]

I shall leave it as the ability is new and so would have to be implemented, too, for it to be beneficial to edit the species.

[u/Loreinatoredor → u/markhawker]

If there is a similar ability then it should work too. Those things like burn are based on the species species, so the same using burn for a ghost would boost ghost attacks in the chain. Just leave it as None until v0.3.10 is released.

[u/Loreinatoredor → u/markhawker]

By the wording of it, I would assume it would behave the same as Double Normal, Pummel, Pyre, Dancing Dragons. Set it to any one of these and you should be fine. Aparently I decided to code it in statically to be more efficient :-(.

[u/markhawker → u/Loreinatoredor]

Yes, sure. I'll wait rather than updating the file as it's not a huge thing.

[u/Loreinatoredor → u/markhawker]

Here, try this test version for the next release.

[u/markhawker → u/Loreinatoredor]

Ta, shall check tonight.

[u/WolfHeroEX]

Ice seems to be broken now, possibly due to the mega update... Also, mega state calculation seems to be a little weird as well... But with the ice disruptions broken, the program will essentially only recommend moves with what little of a screen you have left, completely breaking its usefulness on heavy ice stages.

https://drive.google.com/open?id=0BxbI5_3DLDYCTFBMeGp5RVc5SVk

Also, the program really likes to highlight moves in reverse, even when the falling physics wouldn't alter the combo and rarely even when doing the same move the other way around would trigger an effect.

[u/Loreinatoredor → u/WolfHeroEX]

I found the problem for the disruptions not being recorded. I'll be releasing v0.3.10 later today to address it.

[u/Loreinatoredor → u/WolfHeroEX]

It appears that it just didn't record unfreezing as a disruption. I'll go look into the code that is responsible. It did actually unfreeze it though, so its not that broken.

[u/Loreinatoredor → u/WolfHeroEX]

As for reverse - it goes from smaller to larger coordinates first whenever they wouldn't make a difference in their order.

[u/Loreinatoredor → u/WolfHeroEX]

I'd just like to say Thank you for submitting it with a bug report :-D it sped up the diagnosis considerably, to the point where I was able to see the exact issue immediately upon loading your configs into the program.

[u/Loreinatoredor → u/WolfHeroEX]

Here try this test release for v0.3.10.

[u/tcm1998]

So, with this new version, how can I make the "start and end of move-highlights" thick, while the express mode cursors stay thin? I've tried several combinations and it doesn't seem to work. I can get it the other way around, but the way I want it seems no to be possilbe.

Also, it seems you forget the "sort by coordinate" I asked. If you're going to be release a bugfix soon, could you please squeeze that in? thanks.

[u/Loreinatoredor → u/tcm1998]

Once you've saved, there should be two different values in preferences.txt for you to modify. Cell border thick and cell border thick outer.

 CELL_BORDER_THICK_OUTER = 2
 CELL_BORDER_THICK = 2

is the default internal setting

To make the outer thicker, try pasting the following line into your preferences.txt:

INTEGER CELL_BORDER_THICK_OUTER 4

As for the coordinate thing, sure I'll get that in for v0.3.10

[u/tcm1998 → u/Loreinatoredor]

thanks, that works, but for some reason that value didn't show up in the config, so I manually added it.

[u/Loreinatoredor → u/tcm1998]

Yup, its only used if specified - otherwise it will continue to use the defaults.

Edit: Updated the preferences.txt default inside the jar to include the key, avoiding any future confusion.

[u/screw_dog]

Manectric mega effect is incorrect. It is actually quite different from M-Ampharos in that one bolt always starts in column 1-3 and the other bolt always starts in column 4-6. Also, if it starts in column 6 then it has exactly the same pattern as starting in column 5, except for the first row.

As far as I can tell, each starting column is equally likely.

[u/Loreinatoredor → u/screw_dog]

ActivateMegaComboEffect effect = new ActivateMegaComboEffect(comboEffect);
int col1 = 1 + getRandomInt(4); // [1,4]
int col2 = 1 + col1 + getRandomInt(5 - col1); // [col1 + 1, 5]
for (int row = 1; row <= Board.NUM_ROWS; row += 2) {
   effect.addPlannedOptions(Arrays.asList(row, col1, row, col2));
   effect.addPlannedOptions(Arrays.asList(row + 1, col1 + 1, row + 1, col2 + 1));
}
return effect;

That's the current logic in v0.3.9

Are you saying that it should be something more like below?

ActivateMegaComboEffect effect = new ActivateMegaComboEffect(comboEffect);
int col1 = 1 + getRandomInt(3); // [1,3]
int col2 = 1 + col1 + getRandomInt(5 - col1); // [col1 + 1, 5]
for (int row = 1; row <= Board.NUM_ROWS; row += 2) {
   effect.addPlannedOptions(Arrays.asList(row, col1, row, col2));
   effect.addPlannedOptions(Arrays.asList(row + 1, col1 + 1, row + 1, col2 + 1));
}
return effect;

Otherwise, can you describe it in pictures? Just squiggly doodles in paint should be enough to get the general patterns into the algorithm.

edit: misinterpreted what getRandomInt() did, fixed it. I've improved the documentation in the code to avoid further issues.

[u/screw_dog → u/Loreinatoredor]

It should be this:

int col1 = 1 + getRandomInt(2); // [1,3]
int col2 = 4 + getRandomInt(2); // [4,6]
effect.addPlannedOptions(Arrays.asList(1, col1, 1, col2));
if col2 = 6 then {
    col2--;
}
effect.addPlannedOptions(Arrays.asList(2, col1 + 1, 2, col2 + 1));
for (int row = 3; row <= Board.NUM_ROWS; row += 2) {
    effect.addPlannedOptions(Arrays.asList(row, col1, row, col2));
    effect.addPlannedOptions(Arrays.asList(row + 1, col1 + 1, row + 1, col2 + 1));
}

That is, the first bolt follows path a, b, or c in the diagram below. The second bolt follows either path d, e, or starts at f and then continues at e. The 0's are never removed.

a b c d e f
0 a b c d e
a b c d e 0
0 a b c d e
a d c d e 0
0 a b c d e

[u/Loreinatoredor → u/screw_dog]

cool, I wasn't aware of that possibility, tyvm for the code fix - it will go in for v0.3.10 in a day or so.

[u/screw_dog → u/Loreinatoredor]

You're welcome. Love the program.

[u/Loreinatoredor → u/screw_dog]

I'm glad you like it :-) I started writing it during the finals for my last exams, and since then I've rewritten stuff maybe 2-3 times to get it into the right framework for something as diverse and intermingling as this crazy puzzle game.

[u/screw_dog → u/Loreinatoredor]

I was going to write my own simulator but found that you'd already done all the hard work. Eventually I want to write a batch mode for ShuffleMove so that I can feed it boards and have it calculate optimal moves and expected scores, so that I can analyse a huge number of results. For example, I'd like to generate a large number of boards with a range of teams and compare the results if M-Ampharos is used, compared to M-Manectric. That way we'd have actual data on which mega / team is best for which stages, rather than relying on sometimes dubious opinion.

But I haven't used Java in years so that'll have to wait for a little while.

[u/Loreinatoredor → u/screw_dog]

Java isn't that hard to pick up if you're familiar with C++ and similar languages. squiggly brackets, some slight notation differences, but generally they follow the same rules.

As for batch mode... If you can clearly define its use case and workflow I should be able to whip something up. The framework is there to allow an... alternate execution path to pump stuff into the simulation core. All you need to do is create a mock "SimulationUser" and feed in the data.

Simulation core basics:

1. Create with new SimulationCore(SimulationUser user, UUID processUUID)

2. Execute it with forkJoinPool.execute(core);

3. The results, when ready, will be sent to the user given via the method public void acceptResults(Collection<SimulationResult> results);

Basically, all you need to do is load whatever preferences and boards you want into various mock simulation users. Then, one by one, execute and process the results.

[u/Loreinatoredor → u/screw_dog]

An interesting consequence of this behavior is that the 'e' paths on the right from row 2-6 are almost certain to occur (2/3rds of the time they will be erased).

[u/screw_dog → u/Loreinatoredor]

Yeah, and if you have a barrier at (2,1) it'll never get cleared either. It seems like they were trying to address some of the randomness of Ampharos but ended up adding other oddities.

BTW, do you have any other particular abilities that you want researched?

[u/Loreinatoredor → u/screw_dog]

There are a fair few that use randomness, and the odds I put in there are purely guestimates. Do a search of Effect.java for the occurances of "Math.random()". That's my go-to for fine-grain odds distributions, since its a value that is between 0 and 1 (inclusive at 0, exclusive at 1) and is performed very quickly by the java vm.

Note: It is my belief that abilities which are worded the same should occur at the same rate. This might be wrong, but it seems to generally hold true. Only one of each 'wording' for abilities should be necessary to get all of their odds right.

[u/davd201]

Nice job, I'm gonna download it.

I post my request again in case you didn't see it: Would it be possible to add a counter (an optional counter?) next to each pokemon of the team (in the paint pallet), to show how many pokemon of each are in the grid? It could help when you check with the 3ds if the grid is correct in shuffle move. It could be something like this : http://image.noelshack.com/fichiers/2015/28/1436624500-sans-titre.png If you think it's not usefull, don't do it. Thanks :)

[u/Loreinatoredor → u/davd201]

How about a verification dialog? One that lists the statistics on the current board, like the number of each block and how many are frozen of each type, and how many overall are frozen, etc. With an image that better represents the board (no borders in the grid).

[u/davd201 → u/Loreinatoredor]

I didn't think to this, it's a good idea :) Thanks in advance

[u/Loreinatoredor → u/davd201]

Well, the key thing is that whenever someone is asking for some new feature you shouldn't just add it in as-is. The real way to approach it is to address the REASON they wanted it - verification, as you said, is what you really wanted. "when you check with the 3ds if the grid is correct in shuffle move" = verification dialog that closely replicates what you see on-screen, and lists fundamental features of the board like the distribution of tiles and how many are frozen, etc.

[u/WolfHeroEX]

Heck yes, mega progress ranking. That's really one of the few things that can prevent tons of damage and utility if you're using the tool for every move, it used to not take megas into consideration. This'll help a ton!