Skip to content
This repository has been archived by the owner on Jan 23, 2024. It is now read-only.

Version 5.5.2! #1095

Merged
merged 57 commits into from
Jan 30, 2021
Merged

Version 5.5.2! #1095

merged 57 commits into from
Jan 30, 2021

Conversation

lramati
Copy link
Contributor

@lramati lramati commented Jan 27, 2021

  • Mega Energy, XL Candy support, including new layout
  • Lv50 support
  • Gen6 pokemon
  • re-targeted to Android 10 to allow continued Play Store updates

Unfortunately PokeSpam had to be disabled and PokeBattler is still horribly out of date. Recalibration is also extremely finicky right now, hoping to fix that in v5.5.3

nahojjjen and others added 30 commits October 28, 2018 16:56
Adds CpM, Candy and Candy XL values for levels 40.5 to 50. Still needs
an update to actually scan Candy XL and Mega Energy.
It also redoes how it determines the costs. Instead of doing the candy
costs again somewhere else, reuse the array from the Data class. It also
stores all costs into the UpgradeCost class.
Sometimes it reads wrong values (especially 0, 0, 0) and in those cases
it might be handy to manually restart appraisal scanning.
It downloads a CSV from Google Sheets with the names and translations of
them and creating the corresponding XML files.
    Zygarde has a uniqueId of "YVELTAL" for some reason, putIfAbsent
    prevents overwriting (Although only if Yveltal shows up first, which
    is the case in the current GM, and the best generic fix I can think
    of for now)
    Had to update Meltan and Melmetal offsets
xZise and others added 27 commits December 29, 2020 18:27
A trainer with a level below 40 cannot power up a pokemon with a level
above 40. So the maximum pokemon level has two maximum values.
When switching from Appraisal to Input, it would loose the selected
Pokemon and select the originally selected one. It now uses the stored
Pokemon when opening the Input fraction.
When changing the Pokemon name in the text field it wasn't actually
updating the prediction accordingly. It also removed duplicated code and
does show the same button text when the scan failed.
old implementation of fixOcrLettersToNums could cause logic to think
it found a good value when reading garbage, which would break scanning.
New version is more robust (but likely not perfect)
default "" input handled differently, will never return null
This solves the timing issue with creating ScreenGrabber
@lramati
Copy link
Contributor Author

lramati commented Jan 27, 2021

Contains and closes #1089

@lramati
Copy link
Contributor Author

lramati commented Jan 27, 2021

I think the build failed due to mismatched gradle versions?

@nahojjjen nahojjjen merged commit dbffaff into farkam135:master Jan 30, 2021
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.

4 participants