Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[enhancement] onLevelingUp #105

Open
M1L4 opened this issue Sep 14, 2017 · 0 comments
Open

[enhancement] onLevelingUp #105

M1L4 opened this issue Sep 14, 2017 · 0 comments

Comments

@M1L4
Copy link

M1L4 commented Sep 14, 2017

[Problem]
There is no easy way for member specific evolving.

[Description]
Assuming we want to level fast and disable AutoEvolver and reach the level range of around 98. At that point we would love to enable the auto evolver function again, to get a fully evolved pokemon once we reach lv 100. There are several ways to achieve this, but also problems associated:

  • testing team level during onPathAction: once highest lv pkm reaches lv 98 enable evolve
    • Problem: mixed teams - if highest is 98 and all others lowleveled, evolve would still be enabled
  • testing member specific level: To identify which pokemon leveled up, at least experience must be tracked. Difficult, but still manageable
    • Problem: What about lv 5 pkm and lv 98 pokemon leveling up during same fight?
  • onSystemDialog catching: not sure if this even works, but assuming level up would generate a dialog, search the matching teammember, check conditions and anser dialog in response
    • Problem: Dialogs tend to use the pokemon name, which could possible have multiple matches in a team.

[Suggestion]
AutoEvolver already posses the ability to register a level up. Forward this information to the scripter to manipulate it's behaviour. Fitting to the current namestyle, e.g.:

bool OnLevelingUp(int teamIndex)

Which could be manipulated by scripter like this:

function onLevelingUp(teamIndex)
    if getPokemonLevel(teamIndex) > 98) then return true end
    return false
end
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant