User talk:Magevideogames

Welcome to Pokemon World Online Wiki! We hope you will contribute much and well. You will probably want to read the help pages. Again, welcome and have fun! Ciaossu ~ Reborn (talk) 23:40, 2 January 2014 (GMT)

PokemonRawList

Heyo,

I've read over the raw-data list (for Pokemon) and noticed that you've appended list with new columns/variables—much of which will come into use later. As helpful as I find much of this data, for future applicability on some templates, there are some columns that I'd advise removing and changing.

For starters, some parameters are redundant, simply because they can be converted into other values, simply by using a value that's already provided. By using the formulaic mechanisms of some templates, which I intend to do with some future templates that I intend to construct, parameters such as the Pokemon's experience at level 100, and one value on the gender ratio, will not be necessary; I'll elaborate in following paragraphs, and advise which parameters to remove.

I would advise removing the column for a Pokemon's total experience at level 100, firstly. #expr statements can be added in templates to string together the same formula used for the leveling system, to determine the amount of experience required to reach a level (100 in this context). Therefore, only the Pokemon's base experience would need to be on the data list; the total amount of experience at level 100 would be determined template-side, and is unneeded on the raw-data list.

Additionally, the base experience values of Pokemon themselves are subject to change, thus equating to a different total amount of experience at level 100. If the total amount of experience is removed, only the base experience on the list would need to be changed, but templates would still calculate the correct amount of total experience once that base-experience value is changed accordingly.

Secondly, only the gender ratio - male, out of gender-biased selectivity (:P) - would be needed on the list as well. Percentages only go up to 100, therefore only one value in the diametrical ratio would be needed; if 87.5 is used for one ratio, a template can determine that the remainder is 12.5, thus it'd automatically use the remainder to display the female ratio. Bottom line: the female ratio can be removed from the list.

Lastly, regarding the rarities of the Pokemon, I intended to set those up as boolean-type variables - simply plugging in "Y" or "N" variables, depending on if the Pokemon is available in-game or not, respectively. The rarity system in itself is being reformed, so the rarity tiers themselves may not be applicable at this time, but we'll be able to change those at a later time - it's just important to be that Pokemon are flagged as available or not on that page at this time.

Thanks again for adding them, but I would advise to remove and revise the redundant variables if needed - which should be easy, if they're still saved on your spreadsheet. :P I just prefer that the page is more spacious itself with how many variables are plugged into it, so it's more easily manageable for what variables will be of more importance.

Naero (talk) 03:29, 10 March 2014 (GMT)

I've noticed you've compressed it of the redundant categories I've advised against, and I'd like to thank you again; I'm hoping to put this categories to use soon, hopefully once I devise templates that'll utilize them more facilitatively. :) Naero (talk) 02:36, 11 March 2014 (GMT)

Move-technique descriptions.

Yo,

Just as a reminder, I would be more second-thinking on copying/pasting the official move descriptions into the move-information templates. Under a completely developed, blemishless battle system, I would not mind them; this is not the case at this time, however, since move descriptions will need to differ here, due to bug-impaired functions of moves in this battle system.

For the Move Description field in my template, I prefer that it describes the move exactly as it functions within PWO's capacity—due to limitations, they do functionally differ from the handheld games, and must be described accordingly. Only if the move is completely bugless, in which the "Mechanical Limitations" field would not contradict the official move description, I would be fine with adopting official move descriptions.

Example: Rock Slide's official, unmodified description mentions that it causes the user to flinch, but that tidbit is debunked in the Mechanical Limitations section.

Thank you for your contributions nonetheless, but I would advise to be more thoroughgoing and selective on which moves you choose to use the official descriptions from.

EDIT: Furthermore, I'm iffy about using the official move descriptions altogether. They tend to give more of a surreal metagame description behind them, whereas descriptions documented by Bulbapedia (citing another model that I'd like us to follow after for move descriptions) tend to be more informative. Example: Flamethrower's official description, while it has a more metagame-sound context, might not provide the specifics that players may be looking for (ie. it mentions that the move can burn the target, but it doesn't mention that it's a 10% chance to burn the target, which is considerably sought-out information).

EDIT2: Sorry if I'm coming across as a bit of a control freak, but it's just apart of my perfectionistic, micro-analytical mindset. :P Naero (talk) 03:19, 14 April 2014 (BST)