Abyss Engine

Rust core · C# gameplay · Built on Bevy

Mistakes show up when you build, not when you play

Abyss Engine runs your C# gameplay on a native ECS built on Bevy. Assets, input actions and layers are typed keys rather than strings, so a typo is a build error at the line that made it, not a null reference three scenes later.

Checked when you build

The well-known pitfalls, fixed at the root

Engines have long let you name things with strings: a prefab by its path, an input by its name, a layer by its label. Every one compiles, and every one can be wrong, and you find out while the game is running.

Abyss Engine writes a typed key for each of them as you build. A misspelling or a moved file stops the build at the line that names it, and the compiler says which key you meant.

  • Keys for assets, scenes, input actions, layers and UI documents, written from your project
  • Player settings as typed classes, never values filed under string keys
  • 32 compile-time checks for mistakes the engine would otherwise meet at runtime
Spawner.cs
PrefabId enemy = context.Assets.LoadPrefab("enemy");error ABYSS026: 'enemy' is a string, and a game loads an asset by the key the build writes for it: Addresses.Enemy is 'enemy'// By the keys the build writes instead:PrefabId enemy = context.Assets.LoadPrefab(Addresses.Enemy);SceneId level = context.Scenes.Load(Addresses.Levels.First);Vector2 move = context.Input.Vector(Actions.Player.Move);world.SetLayer(bullet, Layers.PlayerBullets);

Native ECS

Gameplay code that runs where the data is

Systems are plain static C# methods, and they run directly on Bevy's component storage: no call across languages for each entity, no copying, and no garbage for the collector to stop the game for.

A system says what it writes and what it reads in its own signature, so the scheduler spreads systems across your cores without locks you have to think about, and a game ships as one native executable.

MovementSystems.cs
public static partial class MovementSystems{    // ref writes, in reads: all the scheduler needs.    [AbyssSystem]    [MethodImpl(MethodImplOptions.AggressiveInlining)]    private static void Integrate(        ref Position position,        in Velocity velocity,        in SystemContext context)    {        position.X += velocity.X * context.DeltaTime;    }}
a frame for a thousand lit, rotating cubes
1.27 ms
interop calls per entity
0
games compiled to native code
AOT

Frame time measured on an RTX 5080 with vsync off.

Modular

Built from packages, open to other people's code

Beyond the core, the engine comes as packages: folders with their own assets, shaders, scripts and Rust, installed and updated from the registry in the editor's Package Manager. Physics is two of them, on Box2D for 2D and Jolt Physics for 3D.

Your packages can use NuGet packages, and your game can carry Rust crates and Bevy plugins of its own. Nothing is locked behind the engine.

packages/
  • abyss.physics2d2D physics, on Box2DAbyss Registry
  • abyss.physics3d3D physics, on Jolt PhysicsAbyss Registry
  • studio.weatherA package of your own, or anyone'sMy Assets
  • NuGet & Rust cratesLibraries your packages and game bring alongTheir ecosystems

Open source

Open source, and built on Bevy

Abyss Engine is licensed under MIT or Apache 2.0, at your option: the same terms as Bevy and most of the Rust ecosystem. Bevy is an unmodified dependency, not a fork, so the engine moves forward with it.

The source goes public on GitHub with the first release.

SPDX-License-Identifier

MIT OR Apache-2.0

Built on
Bevy, as an unmodified dependency
Source
Public on GitHub with the first release

Backed by a company

A real counterpart for your studio

Abyss Engine is developed by Null Software LLC, a registered company in the United States. Studios that build on it get commercial support and direct contact with the people who write the engine.

Null Software LLC

Roswell, Georgia, United States

  • Commercial support for studios
  • Direct contact with the engine's developers
  • A company accountable for the engine's future
support@abyssengine.net

This website

Your Abyss Engine account

abyssengine.net is the home of Abyss Engine. An account here is what you use the engine's services with: the packages and project templates you own, the ones you publish under your own or your team's name, the access tokens your build servers download them with, and messages to our support.

You sign in with your email address and a password, or with your Google or Apple account. From Google or Apple we receive only your account's id there, its email address and your name, and we use them only to sign you in: never for advertising, never sold or shared. Our Privacy Policy says what we keep and how to delete it.

With an account you can

  • Get packages and project templates, and download those you own
  • Publish your own, as yourself or as a team with roles for each member
  • Make access tokens for build servers and CI
  • Write to our support

Delete your account at any time, from its profile page.

Building something, or thinking about it?

Tell us what you are making and what you need from an engine.