Sunny framework for fighting game built on top of Bevy.
Find a file
Helio Nunes Santos 5aef760241 Updated refs
2026-04-12 16:43:11 +02:00
sunny_framework_extra_maths@5d6e5625ac Added license and README.MD 2026-01-19 13:46:23 +01:00
sunny_framework_input_system@be04be5b50 Updated refs 2026-04-12 16:43:11 +02:00
.gitignore Updated refs. Added script to test. 2026-02-01 11:00:18 +01:00
.gitmodules Changed to use events for reading keyboard, apart from adding gamepad inputs 2026-03-15 21:14:02 +01:00
build.sh updated refs 2026-03-27 12:29:24 +01:00
Cargo.lock AAA 2026-04-12 16:41:32 +02:00
Cargo.toml Changed to use events for reading keyboard, apart from adding gamepad inputs 2026-03-15 21:14:02 +01:00
LICENSE Added license and README.MD 2026-01-19 13:46:23 +01:00
README.MD Added license and README.MD 2026-01-19 13:46:23 +01:00
run.sh updated refs 2026-03-27 12:29:24 +01:00
test.sh updated refs 2026-03-27 12:29:24 +01:00

Sunny Framework

Sunny framework is a framework for developing mainly 3D fighting games on top of Bevy. It is named Sunny because my name is Helio and it means 'the sun'. It is inspired by the idea of M.U.G.E.N. which allowed users to develop fighting games, albeit in 2D.

Goals

Provide a suite of libraries and tools for developing 3D fighting games, such as libraries for input, scripting, networking among others. It doesn't aim to replace components of Bevy or rework something unless necessary. In fact, if Bevy develops systems that are more suitable for the goal of developing 3D fighting games, a system might get completely ditched. Also, one of its goals is to allow fighting games to developed in such a manner that engine recompiles are not necessary, through the use of scripting and dynamic systems.

Contributing

All types of contributions are welcome, from ideas, wishes (of course not all can be granted, but knowing what users think is necessary for a good framework is good) and code. If you have an idea or want to take the task of a new system, open an issue on the framework repo. For improving/taking tasks on systems, open an issue on the system repo and do pull requests there. The main repo will be mainly setup to run CI/CD and publish new versions of the crates on crates.io (for now while it is extremely experimental it will not be submitted to crates.io at all).

Dependencies

Introducing new dependencies is allowed, with caveats, as follows:

A) Dependencies must have permissive licenses such as MIT or BSD. B) Compile times must be watched carefully, as Bevy is already known for having a quite lenghty compile time.