#assets #bevy #game-assets #gamedev #game-engine #otbr

nightly ryot

MMORPG library based on the concepts of open tibia written in rust and bevy

5 releases

0.2.2 Apr 13, 2024
0.2.1 Apr 13, 2024
0.1.5 Feb 7, 2024
0.1.4 Jan 29, 2024

#1022 in Game dev

Download history 3/week @ 2024-01-21 26/week @ 2024-01-28 2/week @ 2024-02-04 2/week @ 2024-02-18 3/week @ 2024-02-25 70/week @ 2024-03-03 4/week @ 2024-03-10 156/week @ 2024-04-07 212/week @ 2024-04-14

368 downloads per month
Used in ryot-assets-cli

MIT/Apache

265KB
6.5K SLoC

Ryot

Ryot! An open tibia based MMORPG library in Rust.

MMORPG library based on the concepts of open tibia.

Ryot is an event-driven library that provides simple utilities for building OT based games. It is designed to be used with the Bevy game engine. It is currently in early development and is not yet ready for use.

Ryot is design to integrate with OpenTibia concepts, facilitating the creation of games that intend to use CIP-like contents/assets formats, as well as some game mechanics.

It provides a major component:

  • ContentAssets - A collection of content assets that can be loaded into the game, including appearances.dat, catalog and configs.

It also provides some utilities:

  • Appearance - A collection of structs and utilities used to manipulate protobuf based appearances, including Prost generated structs from the appearances.proto file.
  • Bevy Helpers - A collection of helpers that can be used to send async events, load configurations, appearances, sprites and contents as BevyAssets.
  • Compression - A compression utility that can be used to compress and decompress sprite sheets.
  • ContentBuilder - A builder that can be used to build content assets from the CIP client content folder, decompressing sprite sheets and copying the necessary files to the assets folder.
  • Sprite Utilities - Functions that can be used to decompress, manipulate and load sprite sheets as game assets, taking into considerations CIP-like sprite sheets structures.
  • Content Utilities - A collection of structs that can be used to manipulate contents, including configuring and loading them.

Dependencies

~64–110MB
~2M SLoC