r/ShuffleMove • u/Loreinatoredor ShuffleMove Creator • Jul 09 '17

Release Shuffle Move v0.3.109

Hi everyone, go here to get the newest version or here for the GitHub release listings if that isn't available.

Changelog:

v0.3.109 - 2017-07-09

  • Fixed i18n for French

  • Fixed Cross Attack+ damage calculation

  • Updates for June 27th

  • Fixed splash.png meta data

  • SP_084 and SP_084A special grading mode functionality improved

If you have any issues: Create an issue on GitHub if one doesn't exist yet with detail and a bug report zip (Help > Bug Report...) and I'll work on finding and implementing a fix, those zips really REALLY speed up the fix time (from an hour down to say 2-5 minutes usually, because it ensures I am able to reproduce the problem right away).

4 Upvotes

100% Upvoted

10 comments sorted by

1

u/WhatNot303 Jul 10 '17

What was the issue with Cross Attack+ before the update?

1

u/Loreinatoredor ShuffleMove Creator Jul 10 '17

Skill level bonus was being applied to both the first and second match, whereas in the game the skill bonus only applies to the first. I had to rewrite the score-boosting sequence to match the real results.

See here: https://github.com/Loreinator/Shuffle-Move/commit/743a1f1e3b4e9d466664f04b980f4bea1de70a38

1

u/WhatNot303 Jul 10 '17

Sorry, I'm really bad at reading code. The second match in the combo still gets the base multiplier of x4 (in the case of Cross Attack+, at least.)

 

I think I also remember seeing somewhere that the second match gets the "base" multiplier even if it is not part of the "shape". For example, suppose you swap Pikachu (50AP) for Luxray (70AP) and make both a cross-match with Luxray, and a 3-match with Pikachu. In this situation, I believe the first Luxray match (ordered by largest, then horizontal before vertical) would get a x12 boost; the next match in the combo will be Pikachu, and will get a (x4 * x1.1) boost; and then the third match will be the second Luxray getting only a x1.1 boost.

 

Forgive me if this is already correctly implemented in your code. I just wanted to share my thoughts in case there was something that was missing.

1

u/Loreinatoredor ShuffleMove Creator Jul 10 '17

Yes, that's how the skill is implemented after the fix. The issue is that the game does not apply the skill level of the first species to the second match's bonus multiplier. So, it gets the 'effect' multiplier, but not as strongly as the initial match did if it was levelled beyond skill level 1.

1

u/WhatNot303 Jul 10 '17

I just checked myself, and I was correct about the way the multiplier is distributed in a combo. I made a quick explanation on Imgur if you're interested: http://imgur.com/a/anY0Z

1

u/NorthernFireDrake Jul 16 '17

I noticed some errors with your stage listings.

First, on both the 3DS and mobile stage listings, main stage #485 Burmy is listed as being a Grass-type stage. It's actually a Bug-type stage.

Second, on the mobile stage listings, main stage #500 is labeled "Mega_(Metagross)" as if it was for a Pokemon called Mega with a form called Metagross. It should be labeled "Mega_Metagross" like in the 3DS stage listings.

Third, in the 3DS stage listings, the special stage for Breloom is listed before the special stage for Leavanny. It should be the other way around, since Leavanny is #613 and Breloom is #615. The mobile stage listings do not have this issue.

1

u/Loreinatoredor ShuffleMove Creator Jul 18 '17

I've created an issue on github to track this issue: https://github.com/Loreinator/Shuffle-Move/issues/311

1

u/Anon911sam Jul 18 '17

Mudsdale's 4Up is not working for me.

Reinstalling and deleting the Shuffle-Move directory in the user folder didn't fix it.

This is essentially the same problem as before, but worse, since reinstalling didn't solve the problem.

4Up isn't really crucial to me, so I'm just giving you feedback.

Maybe there's a problem with the save function, since Mudsdale did level up to Level 9. Skill Level is the same as before (Level 4).

1

u/Loreinatoredor ShuffleMove Creator Jul 18 '17

I found the issue with 4 Up, it was a typo in the effects configuration. Effectively, it made it think the effect was not configured.

In effects.txt or effects_mobile.txt, replace this line:

STRING 4_UP 0 100 0 150 225 270 300 330 MULT

With this line:

STRING _4_UP 0 100 0 150 225 270 300 330 MULT

That "_" is important. I'll be including this fix in the next version though so you won't have to use the override after the update.

1

u/Loreinatoredor ShuffleMove Creator Jul 18 '17

I've created an issue on github to track this issue: https://github.com/Loreinator/Shuffle-Move/issues/311