dqsdhr / classicsim

An event-driven simulation tool written in C++ for World of Warcraft Classic.

Introduction

This is an event-driven gameplay simulator for World of Warcraft Classic written in C++. It is called "ClassicSim", or CSIM for short. Its purpose is to provide feedback to a user regarding the value of equipment, talents, consumables, rotation choices, etc.

For information regarding new features / bug fixes in upcoming release, check Next release.

Licensing

Licensing information can be found in LICENSE.md.

Downloads

Releases are available at the ClassicSim website.

Features of this tool

These are some of the features of this tool:

• Talent calculator (try shift-left/right click talents)
• World buffs and consumables
• Enchants
• Rulesets (Standard, Vaelastrasz, Loatheb)
• Equipment sheet (with full stat filter support)
• Data-driven rotations
• Statistics

Mechanic implementation details

Interested in how certain mechanics are currently implemented? Check Mechanics Details in the wiki.

Future work

See the Release Roadmap for information regarding the upcoming releases.

Next release

Upcoming features and bug fixes that are merged but not yet built and made available as a release:

None (available release is up to date with the latest on master).

Q&A

Q: When is class X or specialization Y supported?

A: See the Release Roadmap for information when specific classes/specs are planned to be supported.

Q: What is the proc chance of Ironfoe or other procs?

A: Ironfoe has at the time of writing a 4.0% proc chance. Most procs uses proc rates from private servers, but you can change the 'rate' attribute in the .xml files. Try a 100% proc rate Ironfoe!

Q: How is this or that mechanic implemented?

A: Check Mechanics Details in the wiki for fairly detailed information regarding how important mechanics are implemented.

Q (not really a question): This mechanic is implemented incorrectly!

A: Open an issue describing the deviation and provide proof of the actual behavior.

Q (not really a question): It crashed!

A: Please let us know what you were doing! Open an issue describing the procedure, and attach saves under <classic-sim-directory>Saves/ (at least GUI + the class you have active).

Q: Why do this..?

A: To satisfy the academic curiosity that literally dozens of us feel.

Credits

Thanks to all the theorycrafters over the years that have tirelessly worked towards refining our understanding of the game.