Skip to content
This repository was archived by the owner on Oct 7, 2025. It is now read-only.

Conversation

@crhbetz
Copy link
Contributor

@crhbetz crhbetz commented Aug 1, 2021

With UIV enabled in PD, it is no longer necessary that an iv_mitm worker only encounters its scheduled specific pokemon at the target location. Instead, it can jump to the locations and just encounter every mon there. This is accomplished by telling PD
it's in mons mode while MAD still schedules the iv_mitm area as usual.

Using a iv_mitm optimized IV List as usual, but with all_mons enabled, will still have the worker teleport to desirable mons on priority, but encounter every mon at the location.

With UIV enabled in PD, it is no longer necessary that an iv_mitm worker
only encounters its target mon ID. Instead, it can jump to the locations
and just encounter every mon there. This is accomplished by telling PD
it's in mons mode while still scheduling iv_mitm as usual.
@ChaosEmpire
Copy link

will this cluster with other iv mitm events in reach?
if so, maybe maltes "old" code to search nearby pokemon could now get more usable

@crhbetz
Copy link
Contributor Author

crhbetz commented Aug 1, 2021

It does nothing but tell PD to encounter every mon it sees (that's in the IV list) instead of explicitly one.

@domizei385
Copy link
Contributor

👍

@ChaosEmpire
Copy link

works great, please merge

2022-02-21 'upstream/master' into iv-mitm-scanmode
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants