开源战役模拟器, Rankings & Team Building for Pokemon GO PvP
PvPoke.com is a resource for Pokemon GO PvP that includes a battle simulator, rankings, and team building. The project’s goal is to provide tools and insights to help players build their teams, and foster the game’s community spirit by making all of the underlying code public. I hope this project can inspire new tools or benefit the existing ones that continue to enhance our enjoyment of the game.
This started as a passion project that went from “I wonder what this would look like quick” to “uh oh, people are going to actually see this.” Just so you know what you’re getting into.
See the Installation section of the PvPoke Wiki.
It was about 10 minutes into development when I realized this project would be great in Angular, but that was unfortunately 5 minutes past the point I was willing to backtrack. So allow me to show you the result.
Here’s a rundown on how most of the pages operate:
GameMaster.js loads the data/gamemaster.json file, which contains all Pokemon and move data. This is our model.GameMaster.js calls an interface object from one of several script files in the /js/interface directory to initialize. This object does things like populate dropdowns with data, create event listeners, etc. These are kind of extensions of the view.Battle.js or TeamRanker.js to receive user input, process it along with the model data, and return results to be displayed by the interface. These files are like the controller.It’s something just close enough to MVC that I get to pat myself on the back, but Javascript and encapsulation go together like spaghetti and other, worse spaghetti. If you’ve heard of spaghetti code, this is more like lasagna code—it’s got structure but might fall apart when you fork it.
Rankings can be generated locally using the following steps:
ranker.php page.ranker.php page will generate rankings for every league and category, and save the JSON results to the /data directory.rankersandbox.php page./data/overall directory.Feel free to copy the Ranker.js or RankerOverall.js files and experiment with your own modifications or algorithms.
I’m excited to work and collaborate with everyone who wants to be a part of this project, big or small. After all, I’m just a Pokemon fan probably like many of you. In this section, I want to be clear about the vision and scope I have in mind for this project to properly set expectations about contributing code, what may or may not be accepted, etc.
The PvPoke Wiki has resources to help run and modify your own local version of the website, or help contribute code.
My work on this project is strictly volunteer, and I have a limited number of hours I can dedicate to it during the week. This may mean some delays related to pull requests, issues reports, etc. I appreciate your understanding and patience! As necessary, I may look to partner with someone or multiple someones to help with any backlog.
You’re welcome to dedicate as much or as little time toward the project as you like, and contribute often or even just once. And if you have to step away for any reason, we’ll send the Beedrill swarm after thanking you for your contributions. It’s only fair.
This project operates on a two-week development cycle. I guess they’d be called “sprints” but sometimes an easy jog is nice, too. This development cycle looks like:
Some tasks may supersede this development cycle, such as fixes for critical issues or data and ranking updates for newly released Pokemon, moves, or mechanics. Some tasks, such as new tools or features, may also take longer than a single cycle. In this case, we’ll do our best to segment that task into individual milestones that can be completed in a two-week period.
Here are examples of some things that would be appealing code contributions and readily fit within the development cycle:
Meanwhile, here are some example items that would be out of scope or don’t align with the project vision at this time. If user or contributor feedback suggests otherwise we can certainly revisit them, but for now I’d like to steer clear of things like:
I appreciate your understanding if a request is rejected. A rejection doesn’t mean that your code or idea is bad, just that it might not fit the current project. I will likely be taking things slow at the start. If you have any thoughts or ideas, I’d be happy to discuss them prior to development so we can work out what might fit best!
And of course, you can always fork the project and develop whatever you’d like. Thanks for reading!
-Empoleon_Dynamite
mglerner has made a Python port of the PvPoke simulation engine, available here:
暂无开放 Issues,或尚未同步最近议题。