Summary
The AD&D Second edition Combat Simulator will run simple simulated battles to determine the statistical likelyhood of success or failure by the party. The simulator does not account for player creativity and uses a very simple method to determine how the battle will go.
Usage
First create a combatants.yaml file with the players and monsters information. The example combatants.example.yaml file included in the package is a good place to start.
Next simulate the war
battle [BATTLES]
The BATTLES argument indicates how many times to simulate the battle. Default is 1.
Configuration
Add all details about the combatants into the combatants.yaml file. The example combatants.example.yaml illustrates the syntax
ac
The values in the AC dictionary are added together to detemrine the AC. For example a shield would have an AC value of 1 because it reduces AC by 1. Studded leather would have a value of 3 because it gives AC 7. If a combatant had both (3 + 1), their AC would be 6. Default is no modifier or AC 10.
attack
This list enumerates the attacks that the combatant will use. The values are the names of the attacks in the attacks section. Each combatant uses all of their attacks each round. For example a monster with an attack list of “claw”, “claw”, “bite” would make all 3 attacks in a single round.
attacks
This list contains all the possible attacks a combatant might use.
damage
This can either be a string or a dictionary. If it’s a string it applies to targets of all sizes. If it’s a dictionary the size of the target is mapped to a damage string.
tohit
The values in the To Hit dictionary are added together to determine the total modifier for the to hit role. For example if a fighter specialized in a bastard sword and had a magical bastard sword +1, the 1 from specialization and 1 from magic would be added to the d20 die roll. Default is no modifier.
rof
Rate of fire can be a number of attacks/shots per round (e.g. 2 or 3) or a ratio of attacks/shots per round (2/1 or 3/2). Default is 1/1.
qty
The number of the given type of monster to include in the battle.
hd
The hit dice of the monster. This can be a traditional Hit Die number (e.g. 3) which is the number of 1d8 dice to roll to determine the monsters hit points, or it can be a traditional Hit Die number with a modifier (e.g. 3 + 2), or it can just be a description of dice and modifiers (e.g. 1d6 + 2 or 2d8)
1 maintainer
Metadata
1 maintainer
Release files for adnd2e-combat-simulator 1.0.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| adnd2e-combat-simulator-1.0.2.tar.gz | 5.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| adnd2e_combat_simulator-1.0.2-py2-none-any.whl | Python 2 | none | any | Details |
Total release size: 13.9 kB
Release files / adnd2e-combat-simulator-1.0.2.tar.gz
| Download URL | adnd2e-combat-simulator-1.0.2.tar.gz |
|---|---|
| Size | 5.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5b363d3040eb8ccd43c77c894c2a99c88c57243cf6e9216037ca5dee6ab27d57
|
|
BLAKE2b-256 checksum How to use checksums |
bc2e858263b48752989bab2822854db143734f03bef6fdb4063ccc852dbf8f6b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / adnd2e_combat_simulator-1.0.2-py2-none-any.whl
| Download URL | adnd2e_combat_simulator-1.0.2-py2-none-any.whl |
|---|---|
| Size | 8.3 kB |
| Tags | Python 2 |
|
SHA-256 checksum How to use checksums |
6eba359329eb782f5273a8a139371bb6f9bbd0af8bfc931bbc99dac0f0609826
|
|
BLAKE2b-256 checksum How to use checksums |
6fea37dcbdac9ba7fa0f3cecedd543b973413b49210e9ffcc132030a9a062384
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for adnd2e-combat-simulator 1.0.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
