Muchlax Tree Calculator

[Quake]

I see this new feature in the main site and have a question. I need slather all the honey trees for the four Munchlax trees have it, or only the four Munchlax trees?

Thanks and good luck with the new site.

[ZMaster]

Only those 4 trees will have Munchlax, if I'm correct. BUT, there is still only a 1% chance you will encounter a Munchlax from those 4 trees. =/

Edited April 10, 2009 by ZMaster

[Zowayix]

Yes.

Also, for the maximum chance, never slather the same tree twice in a row.

If you do the same tree twice in a row, the chance for a Munchlax on that tree drops to 0.1%.

If you encounter one Munchlax, and want another one, make sure you slather it again immediately after the battle. The chance of encountering a Munchlax right after a previous Munchlax is 90.1%.

(This 90.1% chance cannot be SRed. If you are unlucky and get that 9.9% of not being a Munchlax, you are stuck trying for that 1% chance again.)

[Quake]

Thanks to both for the reply, i catch a Munchlax recently.

[glaceon]

what are the 4 munchlax trees?

[xeomyr]

what are the 4 munchlax trees?

it's based on the ID and SID ...

anyway , read the front page dude ^^

[glaceon]

how can I know my secret ID?

it's doesn't let me to convert my sav. file

[ZMaster]

how can I know my secret ID?

it's doesn't let me to convert my sav. file

What is the it's that is not letting you convert your .sav file? Pokesav?

[glaceon]

http://www.shunyweb.info/convert.php#

yesterday I could convert my sav. file and today I can't...

I don't know what's the problem is

[Zowayix]

What format is your save file in?

[kazumi213]

@Sabresite:

A few days ago you explained that the game can handle "problematic" ID combos to always allow for 4 different valid Munchlax Honey Trees to be available to the player.

So I think that there is a little problem with the current calculator, because it is reporting the same tree twice for OTID = 37521, OTSID = 37120. I think one of them should be the 205 *north* one.

[Sabresite]

Yeah its not the calculation, its the output. Its a typo. I will fix it ASAP.

[Sabresite]

Apparently there can be overlap according to SCV. I will update Legal accordingly.

[NovaPhoenix]

This and the honey tree code for Route 207 (one of the legal locations for Munchlax that corresponded with my ID numbers) worked. No need to worry about hunting down anymore of them.

So thanks guys.

[kazumi213]

Apparently there can be overlap according to SCV. I will update Legal accordingly.

So do you mean that there can be less than 4 valid trees after all?

[SCV]

So do you mean that there can be less than 4 valid trees after all?

Yes, I am pretty sure Game Freak was going for always having 4, but in cases like the one you found there can be less than 4, but should always be 3 or more.

This happens in the case when:

Let WWYY be the Secret ID and YYZZ be the Trainer ID.

WWXX YYZZ

If ZZ%15 = WW%14, XX%15=ZZ%15 +1 YY%15=ZZ%15 +2

My guess is that they overlooked this situation (I did as well) when trying to figure out an algorithm that would always get 4 munchlax tress.

[Zowayix]

I'm assuming the WWXX YYZZ is in hexadecimal.

What does the operator % do? I think it's modulus, but I can't remember.

[SCV]

I'm assuming the WWXX YYZZ is in hexadecimal.

What does the operator % do? I think it's modulus, but I can't remember.

Yes, that's in hexadecimal and % is modulus.

[kazumi213]

Yes, I am pretty sure Game Freak was going for always having 4, but in cases like the one you found there can be less than 4, but should always be 3 or more.

This happens in the case when:

Let WWYY be the Secret ID and YYZZ be the Trainer ID.

WWXX YYZZ

If ZZ%15 = WW%14, XX%15=ZZ%15 +1 YY%15=ZZ%15 +2

My guess is that they overlooked this situation (I did as well) when trying to figure out an algorithm that would always get 4 munchlax tress.

I'm not sure whether you have correctly explained this. I can't get the calculator results for the ID combo in my previous post:

TID = 37521 (9291-h) (YYZZ)

SID = 37120 (9100-h) (WWXX)

If ZZ%15 = WW%14 (I guess you mean WW%15) => 13 = 13 (true)

then

XX%15=ZZ%15 +1 => XX%15 = 13 + 1 = 14

YY%15=ZZ%15 +2 => YY%15 = 13 + 2 = 15 (can't be 15)

According to calculator, valid trees are 13 (ok), 0 (ok), 14 (ok), 0 (again)

So your logic explains one of the zeros if we assume that 15 is converted to 0, but not the other (I mean you don't show how one of the 13's becomes 0, if that is what it is happening)

Now if we swap IDs

TID = 37120 (9100-h) (YYZZ)

SID = 37521 (9291-h) (WWXX)

If ZZ%15 = WW%14 (I guess you mean WW%15) => 0 = 14 (false)

then

XX%15=ZZ%15 +1 => XX%15 = 0 + 1 = 1 (doesn't apply, condition is false)

YY%15=ZZ%15 +2 => YY%15 = 0 + 2 = 2 (doesn't apply, condition is false)

Your logic doesn't explain calculator results either: 14 (ok), 13 (ok), 14 (again?), 0 (ok)

[pokemonfan]

Way to confusing for me I'm just going to keep slathering and hope to get a munchlax

Drifloon is easy to find yet rare because it is only a once a day thing. Clearly drifloon is awesome why don't people see it?

[Sabresite]

TID = 37521 (9291) (YYZZ)

SID = 37120 (9100) (WWXX)

( 91 % 15 ) = 13 = WW

( 00 % 15 ) = 0 = XX

( 92 % 15 ) = 14 = YY

( 91 % 15 ) = 13 = ZZ

13 == 0 = false

13 == 14 = false

0 == 14 = false

13 == 13 = true, 13+1 = 14

0 == 13 = false

14 == 13 = false

Final Trees

14

0

14

13

I hope that clears up their stupidity. And Legality Checker is wrong because I did my checks correctly (go figure).

Note: There is one driftloon every Friday. It is not rare because its encounter rating is 100%, and its capture rating is very low.

[kazumi213]

Final Trees

14

0

14

13

I hope that clears up their stupidity. And Legality Checker is wrong because I did my checks correctly (go figure).

Thank you, but Sabresite those are not the trees reported by the calculator for that ID combo, but

13

0

14

0

Now, this is ok:

TID = 37521 (9291) (YYZZ)

SID = 37120 (9100) (WWXX)

( 91 % 15 ) = 13 = WW (different varnames should be used, but anyway)

( 00 % 15 ) = 0 = XX

( 92 % 15 ) = 14 = YY

( 91 % 15 ) = 13 = ZZ

However this is not actually performed by the calculator

(WW==XX) 13 == 0 = false

(WW==YY) 13 == 14 = false

(XX==YY) 0 == 14 = false

(WW==ZZ) 13 == 13 = true, 13+1 = 14 (WW becomes 14)

(XX==ZZ) 0 == 13 = false

(YY==ZZ) 14 == 13 = false

But something like:

(WW==XX) 13 == 0 = false

(WW==YY) 13 == 14 = false

(XX==YY) 0 == 14 = false

(WW==ZZ) 13 == 13 = true, 13+1 = 14 (recheck) (can't be 14) (can't be 15 then 0) (WW becomes 0)

(XX==ZZ) 0 == 13 = false

(YY==ZZ) 14 == 13 = false

for the actually reported trees to be possible, though reported order doesn't match

However your logic explains tree results for the swapped ID case:

TID = 37120 (9100) (YYZZ)
SID = 37521 (9291) (WWXX)

( 92 % 15 ) = 14 = WW
( 91 % 15 ) = 13 = XX
( 91 % 15 ) = 13 = YY
( 00 % 15 ) = 0 = ZZ

(WW==XX) 14 == 13 = false
(WW==YY) 14 == 13 = false
(XX==YY) 13 == 13 = true, 13+1 = 14 (XX becomes 14)
(WW==ZZ) 14 == 0 = false
(XX==ZZ) 14 == 0 = false
(YY==ZZ) 13 == 0 = false

14 (WW)
14 (XX)
13 (YY)
0 (ZZ)

Ok, although the tree order reported by calculator is 14, 13, 14, 0, so I'm not sure what's happening.

But again your logic doesn't explain calculated trees on this case

TID = 21504 (5400) (YYZZ)
SID = 10773 (2A15) (WWXX)

( 2A % 15 ) = 0 = WW
( 15 % 15 ) = 0 = XX
( 54 % 15 ) = 0 = YY
( 00 % 15 ) = 0 = ZZ

(WW==XX) 0 == 0 = true, 0+1 = 1 (WW becomes 1)
(WW==YY) 1 == 0 = false
(XX==YY) 0 == 0 = true, 0+1 = 1 (XX becomes 1)
(WW==ZZ) 1 == 0 = false
(XX==ZZ) 1 == 0 = false
(YY==ZZ) 0 == 0 = true, 0+1 = 1 (YY becomes 1)

1 (WW)
1 (XX)
1 (YY)
0 (ZZ)

Don't match calculator results, which are 0, 1, 2, 3

[mbruno]

I think I found a typo. One of the four trees it told me was "Eterna Forest southeast". I think there's only one honey tree in Eterna Forest and it's not even in the southeast. Unless I'm missing something.

[SCV]

kazumi213 we have not released the full algorithm so that's why things don't match up

[kazumi213]

I know SCV

I saw you starting to speak about it and hoped to "squeeze" a bit more info I understand what you mean.

It's just that I thought that I had figured out how Legal was dealing with ID combo exceptions... until the calculator.

I still can't see how it can apply corrections for certain cases (last example in my previous post, calculator results are the expected ones, ok), but doesn't do the same for the first example and reports the same tree twice. I mean, are you sure is not a calculator coding fault for such special ID combos? Have you actually confirmed in-game that only 3 valid HTs are possible?

I won't post on this again