ppb-mutant
This library provides convenient support for the Mutant Standard emoji for games using the PursuedPyBear engine.
This version is for PursuedPyBear v0.8 and Mutant Standard v2020.04.
Setup
- Install the
ppb-mutantpackage through your preferred package management system. (pip,requirements.txt, pipenv, poetry, etc)
Usage
Demo
A demo showing all emoji can be found by running python -m ppb_mutant.index.
Emoji
You can replace the use of image with an Emoji asset:
class SlimeSprite(ppb.Sprite):
image = ppb_mutant.Emoji('slime')
In addition, the formatting syntax with the variables morph and skin may be
used for Mutant's customization features:
class PunchRightSprite(ppb.Sprite):
image = ppb_mutant.Emoji('fist_facing_right_{morph}_{skin}', morph='clw', tone='r2')
See the modifier guide for details on these.
Alternatively, most customizable emoji also have aliases defined:
class PunchRightSprite(ppb.Sprite):
image = ppb_mutant.Emoji('fist_facing_right', morph='clw', tone='r2')
MorphToneGroup
If you want to change the morph/tone of a bunch of emoji as a group, use the MorphToneGroup:
player_emoji = ppb_mutant.MorphToneGroup(morph='paw', tone='g1')
class HandSprite(ppb.Sprite):
image = player_emoji('hand')
class ProfileSprite(ppb.Sprite):
image = player_emoji('adult')
SelectScene
SelectScene is a base for allowing you to handle mutant morph and tone
(color) customization. It can be used like:
class CustomizeScene(ppb_mutant.SelectScene):
class Sprite(ppb_mutant.SelectScene.Sprite): pass
class BackSprite(Region, ppb.Sprite):
image = Emoji('tick')
def on_button_pressed(self, mouse, signal):
if self.contains(mouse.position) and mouse.button is ppb.buttons.Primary:
signal(ppb.events.StopScene())
def __init__(self, **props):
super().__init__(**props)
self.add(self.BackSprite(position=(-4, 1.5)))
def do_update_morphtone(self):
print(self.morph, self.tone)
For a demo, run python -m ppb_mutant.picker.
Copyright Notice
This library uses Mutant Standard emoji, which are licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.
Development
The image assets are not stored in git.
You can download a copy from the mutant standard website by running build.sh.
Metadata
Release files for ppb-mutant 0.11.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 | Actions |
|---|---|---|---|---|
| ppb-mutant-0.11.2.tar.gz | 13.6 MB | Without provenance | Details for ppb-mutant-0.11.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ppb_mutant-0.11.2-py3-none-any.whl | Python 3 | none | any | Details for ppb_mutant-0.11.2-py3-none-any.whl |
Total release size: 32.5 MB
Release files / ppb-mutant-0.11.2.tar.gz
| Download URL | ppb-mutant-0.11.2.tar.gz |
|---|---|
| Size | 13.6 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b4f8eb9f9b30462824831f8c684f4884ec46363ba1648ca27cc8e5abe401ce2e
|
|
BLAKE2b-256 checksum How to use checksums |
6dbb91570a09cffb7f662613e7b8d0d80f44bea210526ea7af710d9e1a144416
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/3.7.3 pkginfo/1.7.0 requests/2.25.0 requests-toolbelt/0.9.1 tqdm/4.59.0 CPython/3.9.2
|
Release files / ppb_mutant-0.11.2-py3-none-any.whl
| Download URL | ppb_mutant-0.11.2-py3-none-any.whl |
|---|---|
| Size | 18.9 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4e704130b88514c9cdaa7701f7d2660476559574c3caaed51eda1ac996e3b7eb
|
|
BLAKE2b-256 checksum How to use checksums |
2be30292c631cafe90c485b86f8c65346c3d27bc957d8dc7699b3f589a77a90f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/3.7.3 pkginfo/1.7.0 requests/2.25.0 requests-toolbelt/0.9.1 tqdm/4.59.0 CPython/3.9.2
|
Security for ppb-mutant 0.11.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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.