Pokemon Go team builder, training and simulation tool for players who need access to pertinent information related to battling. Enjoy this information and training system that will allow users to calculate IV's as well as study league rankings, "fast-move timing" mechanics, Charge Move Priority(CMP), and battle simulations. This program will soon be able to generate teams and strategies FOR YOU; to help improve your knowledge, skills and performance in this part of the game.

• Background
• Contributing
  • Overall
  • C# Style
  • HTML Style
  • JavaScript Style
  • SQL Style
  • Git
• Credits
• Access
• Team Rules
• Tools
• License

Pokemon IV's, Charge move Priority and Fast-move timing are hard concepts to understand as a beginner or casual pokemon go player. I wanted to know whether I needed my Scrafty for ultra league to be XL'd or "Best Buddies". The process to get the answer to this question was complicated so I decided to create an information and training hub that provides easy access to pokemon data, trends and knowledge that otherwise may be rather... difficult to find.

• PVPoke - json endpoints for league rankings
• PokeAPI - current pokemon go data
• PokeMiners - pokemon go assets and the most recent gamemaster json
• Pokemon Stat product algorythm

• Follow MVC: Model, View, Controller
• Controllers and Models written in C#
• Views Written in HTML, Javascript, and CSS
• Add comments where code might be confusing or to help others understand its purpose

• Curly braces on their own line
• variable names in camel case, no '_' in between words - "variableName"
• Class names must start with a capital and second word is also capital, no '_' in between words - "ClassName"
• Database context will be named db

• Follow Bootstrap formatting
• Follow color schema that is chosen in advance
• id names will be camel case - "variableName"

• Function names in camel case - "functionName"
• Variable names in camel case - "variableName"
• Curly braces on their own line

• Primary keys will be named 'ID'
• Foreign Keys will include the table and ID where it came from - "PokemonID"
• Constraints will be sperated by a '_' - "Pokemon_FK_Matchups"

• Use separate feature branches and send a pull request to dev branch.
• Only commit working code (Unless others require your code to help fix a bug) and commit often.
• Write meaningful commit messages.
• Pull the upstream development code and merge it into your feature branch before submitting a Pull Request.
• Pull Request must be made to the dev branch. All other pull requests will be rejected.
• GitHub Repo Master will merge the dev branch into the main branch after Sprint Meetings

• Reggie Johnson

Website Link - Also Deployed Upon Request!

• Be Kind
• Work Efficiently

• Microsoft Azure
• Identity Framework
• .NET 6
• SQL Server
• C#, HTML, Javascript, CSS
• Continuous Deployment

LGPL-3.0-or-later

For more info see License.md file