Alibi

Attorney Online 2 Server Implementation in C# .NET Core

What is it?

After having ran an Attorney Online server, I despise the current experience of maintaining an active server for this game. So I thought it would be fun to try and make one myself, to see if I can do something better.

Prerequisites

Compatibility

Public builds of Alibi are released for Windows and Linux currently, but the code is not dependent on a single platform and should work on ARM, MacOS, or anything .NET 5.0 supports.

The server itself is compatible with all versions of AO2 that support disabling fantacrypt. (2.4.3+)

Server Setup

Windows:

• All you need is either the Desktop or Core version of the .NET 5.0 Runtime installed.

Linux/Unix:

• Determine how to install the dotnet core runtime on your distribution: here or here are a few.

Usage

To run the most basic possible server, all you have to do is download the latest Release. It will make the needed config files for you and set up defaults for you.

Double click or run this in the console (currently no command line arguments):

Alibi

Documentation:

You can go to the documentation page if you wanna find out how to use the server, make plugins, and the various other articles ill eventually make. However, this page is still WIP, so don't expect a full tutorial.

Plugins

Surprisingly, this thing supports plugins! To make one, just make a new .Net Core Class Library that targets net5.0, and reference the Alibi.Plugins.API project of this repository, or install this NuGet package.

Then, make a class that inherits from Plugin, and implement it's required members, and the constructor. You should now have a bare-bones working plugin! Build it and put the .dll in the Plugins folder of Alibi, and restart the server.

Contributing

I am always open to issues, pull requests, debugging specific issues in private, whatever. I could really use it, actually. My Discord is ElijahZAwesome#6933.

Progress

These features are not implemented:

• Fantacrypt (Probably will never do this as FantaCrypt is gone in 2.9 and noone seems to use pre-2.4.3 clients)
• Slow loading packets are implemented according to everything i know, i have no freaking clue if they work though

TODO

Some shit that needs to get done

• Make websockets less terrible again. Refactored to actually function normally :)
• Add a "primary admin" or something so only they can restart the server and create/remove logins, since mods shouldnt be able to remove mods.
• Multiple levels of permissions, User, Moderator, Administrator
• Switch to an ID system (incremented ID as primary key in the db instead of hwid) instead of this, clients just can't connect and interact with the server unless they have followed the protocol and sent their HWID
• Kick clients without HWIDs
• Clean up some of this shit code
• Become more thread safe (Maybe?)
• Plugins
• Areas
• Case Alerts (CASEA and SETCASE) (Properly implemented, too! +1 Alibi/-1 Tsu3)
• Commands (Some commands are in but need more)
• Logging architecture
• Database
• *I think the command paradigm currently implemented is good enough. Any Tsuserver3 commands that users want can be added by request or through usermade plugins Implement standard commands
• Test/Stress test this bitch
• Document server
• Document Plugin API