Closed BradMackey closed 10 years ago
I have to head out to work in a little bit. if you like, you can start a data branch and start working on an xml for the pokeballs. It will need to be a little different because there is the possibility of multiple different classes for the balls to be constructed in. I think having a second attribute would work well enough for this. I'll leave it up to you but I would consider something like
<root>
<ball name="Pokeball" class="0">
<description></description>
<flashStyle></flashStyle>
<catchRate></catchRate>
</ball>
<!-- More stuff here -->
<ball name="Masterball" class="1">
<description></description>
<flashStyle></flashStyle>
<catchRate></catchRate>
</ball>
</root>
This way when I read it in, I can use the class number as a case for which constructor I send the data to. So class 0 can be the base/standard pokeball class, class 1 can be the masterball class. And as we add more, the file will accomodate.
Alright, I'll get started on that in a little bit.
Pokeball basics implemented.