BYONDTools
==========
A set of tools for BYOND-based games.
Overview
--------
This is a toolkit for developers of BYOND-based games intended to do common, complex
tasks that the engine itself does not currently possess. It also exposes common
interfaces for developers wishing to obtain information from the BYOND object tree,
maps, and DMIs.
Requirements
------------
* Python 2.7+
* Pillow (fork of PIL)
* numpy
Use
---
Initial documentation is taking shape at http://ss13.pomf.se/wiki/index.php/User:N3X15/Guide_to_BYONDTools
API Status
----------
+---------------+--------+
| API Component | State |
+---------------+--------+
| DMI | Stable |
+---------------+--------+
| Maps | Stable |
+---------------+--------+
| Object Tree | Stable |
+---------------+--------+
| Scripting | WIP |
+---------------+--------+
Support
-------
No commercial or official support is provided, but you are free to
submit bug reports or harass N3X15 in irc.rizon.net #vgstation.
================= 0.1.8 - 9/10/2015 ================= * Added support for OpenSS13 to dmmfix * Fixed dmmfix again. ================= 0.1.7 - 3/6/2015 ================= * Added pyparsing-based list() parser to DMM system * DMMFix lives again! * Move from print() to logging for console logging. * Renamed ss13_makeinhands to dmi_compile, now uses a dmi_config.yml file. * Fixed dmindent duplicating proc contents, cleaned out excessive newlines. ================= 0.1.6 - 12/24/2014 ================= * Fixed completely broken map rendering system. * Repaired object tree generation * Fixed color support ================= 0.1.5 - 6/18/2014 ================= * Emergency path fix for Linux ================= 0.1.4 - 6/18/2014 ================= * Added dmm diff and patch commands for patching maps. * Added color name support to BYOND2RGBA. Should fix rendering maps on TG/NT/Bay. * Proper handling of nulls. ================= 0.1.3 - 6/17/2014 ================= * Fixed broken post-install operation on Linux (sorry) ================= 0.1.2 - 6/17/2014 ================= * Fixed line-ending stupidity on Linux * Fixed python trying to interpret DME-derived paths literally (mostly path seperator stuff) ================= 0.1.1c - 6/10/2014 ================= * Missed data directory. Whoops. * Object tree: Fixed mishandling of list() in variables when [ is on the same line. ================= 0.1.1b - 6/2/2014 ================= * Fixed some leftover packaging issues: * post-install didn't create self-executables on Linux, so just calling dmi, dmmfix, etc. wouldn't work. * setup.py didn't specify sub-packages for installation, so installations were fairly broken. * Post-install process now uses sys.executable, rather than trying to figure it out via hackier means. * README changed to reStructuredText for eventual pip release. * Oh my god there's a changelog now * Added MANIFEST.in (fixed a problem uploading *.rst files).
Metadata
Release files for BYONDTools 0.1.8
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 | |
|---|---|---|---|---|
| BYONDTools-0.1.8.zip | 89.7 kB | Without provenance | Details |
Release files / BYONDTools-0.1.8.zip
| Download URL | BYONDTools-0.1.8.zip |
|---|---|
| Size | 89.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
418577e2864b97474fc93bbe2b97ba03055f5069229129ae269be415952d7845
|
|
BLAKE2b-256 checksum How to use checksums |
f1ac6833dbbdd600487061aa863f6ecf9f45bee785553a610f3258b1f2d968bc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for BYONDTools 0.1.8
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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.