A toolset to ease your life when dealing with sprite atlases.
- creates a Ruby source file containing the spritesheet declaration
- readily compatible with DragonRuby's sprite API
- pure core Ruby. No external dependency. Not even Ruby's stdlib. No Regexp.
- a CLI tool that has sex in its name, legitimately
- to integrate to your asset workflow/pipeline or use standalone
- suitable for use with other game engines or other languages (Lua, Rust, you name it I code it.)
- a Pry console to inspect the imported structure, or easily debug issues
- built-in samples (from Kenney ケニー). You can see what it does right away.
gem i zed-spritesheet
[TODO: Explain copy]
Since DragonRuby now has a method to read XML and JSON resources, it is feasible to let the Spritesheet class perform the import directly from a running DragonRuby Game Toolkit game. It is in the works.
However this tool is meant to be usable in various environments, possibly not even Ruby. So, for now, the prefered way is to use the command line tool.
[TODO: Explain ssex tool]
When you're in a high-frequency update cycle, you can opt to let the import/export be handled through Guard
Sure! Just ask away. I'll add whatever language output you need.
You can:
- create a GitHub issue
- send me an e-mail ([email protected])
- chat on the DragonRuby Discord: https://discord.gg/UHrwbVS
Yep! Do you need support for some weird JSON or some antiquated spritesheet from the 80s and can't be bothered to do it yourself?
Send me samples, I'll get you sorted as long as it does not involve EBCDIC.
- Export to Class instead of Hash for DragonRuby
- Tiled JSON tileset format
- ShoeBox JSON format (thanks @booticus for expressing interest)
- Native DragonRuby in-game import
- Output templating to support universal and easy custom outputs
- Viewer (Simple sprite frames visualizer in DragonRuby)
- Single format animation or still without metadata (set a import time)
- Embedded atlas microformat (why doesn't it exist already !?!). I'm aiming for a compact CSV with headers format.
This spritesheet utility set is part of an ongoing project offering turn-key solutions to various basic tasks many game developers face when implementing their ideas.
The ZED Toolset currently include:
- Spritesheet: a language/engine agnostic sprite atlas import/export toolkit (this gem)
- Bezier: a Casteljau/Bezier curves manager and in-game editor for DragonRuby (𝛽)
- GUI: an immediate mode GUI set of objects for DragonRuby (𝛼)
- Utils: miscellaneous classes to make life easier (Timer, TimeBoolean, TimeVal, Color) (𝛽)
- Camera: 2D rich camera class for DragonRuby (pan, zoom, rotate, POI, parallax, motion blur) (𝛼)
- Map: an isometric map class featuring 3D multilayer display sorting (𝛽)
- Path: a multi-agent, 3D path finding class implementing the A* algorithm (prepared)
- Sight: a 2D visibility resolver (planned)
- Maze: an elegant and useful maze generating class that will ease away your stress of the day (𝛼)
- Domain: a boredom resistant Dungeon-like map generator featuring cyclic paths and opinionable randomness (planned)
- Particles: a fast, multi-emitter, faux 3D, particle systems manager (𝛼)
Learn more about the ZED toolset here: https://meuret.itch.io/zed
I have vowed to follow the Semantic Versioning specification 2.0.0 (see https://semver.org/). You can count on it and beat me up when it fails.
Here are my acceptions of some terms I use in version conversations:
- Beta, Bêta (symbol: 𝛽 aka MATHEMATICAL ITALIC SMALL BETA)
Denotes a stable API under final testing. If no bug is found, the code will go out unmodified in an upcoming release that will have the same version number. You may know this state as Release Candidate.
Note that this term does not imply any feature coverage.
- Alpha (symbol: 𝛼 aka MATHEMATICAL ITALIC SMALL ALPHA)
Denotes an unstable API under development. It can change anytime but the associated product should eventually mature and ship. Frankly nobody is supposed to handle these versions. This label is useful for communication.
As semver wishes me to be clear about the API, the supported API is whatever appears when you
run bundle exec rake
in the source directory, except features marked as pending. Note: You can get a
clean copy of this gem source by typing gem unpack zed-spritesheet
.