Different generations #11
Labels
No Label
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: EpicKnarvik97/pokemon-cmd#11
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
EpicKnarvik97 commented on Nov 26, 2017
We could have different methods based on which generation is chosen. The generation would be set in the Game.java file as an enum. If we allow available pokemon and items to be loaded from files, we don't need to consider which pokemon should be available in which generation. If as much as possible is loaded from files (we should also create default files mimicking the original games' behaviour), information about types, type advantages and moves can go in there. Catchrates, exp, and probably a lot of things I am overlooking, need to change according to the generation.
GReaperEx commented on Nov 26, 2017
Hmm, I think it would be easier if we included additional information with each pokemon and not just the name. For example, base stats, evolutions, available moves and at what levels, and even generation.
EpicKnarvik97 commented on Nov 26, 2017
That was what I meant. There is no reason to add it now, because all stats are randomly generated, but when we have constant, but partly randomized pokemon, they should be defined in some kind of file with all necessary information. I don't know how to organize all that information, but we'll se when the time comes.