GameDevWare.Charon
2024.3.6
dotnet add package GameDevWare.Charon --version 2024.3.6
NuGet\Install-Package GameDevWare.Charon -Version 2024.3.6
<PackageReference Include="GameDevWare.Charon" Version="2024.3.6" />
paket add GameDevWare.Charon --version 2024.3.6
#r "nuget: GameDevWare.Charon, 2024.3.6"
// Install GameDevWare.Charon as a Cake Addin #addin nuget:?package=GameDevWare.Charon&version=2024.3.6 // Install GameDevWare.Charon as a Cake Tool #tool nuget:?package=GameDevWare.Charon&version=2024.3.6
Charon - Game Data Editor
<img width="894" alt="dashboard" src="https://raw.githubusercontent.com/gamedevware/charon/main/docs/assets/cover_github.png"/>
Documentation • Discord • Website • Changelog • Issues
Plugins
<img width="100" alt="unity" src="https://raw.githubusercontent.com/gamedevware/charon/main/docs/assets/unity_logo.svg"/> <img width="100" alt="unreal engine" src="https://raw.githubusercontent.com/gamedevware/charon/main/docs/assets/unreal_engine_logo.svg"/>
Standalone
How to start with custom game engine → C# • TypeScript
Summary
Charon is a powerful game development tool that streamlines the game development process. It provides a structured approach to designing and modeling game data, with automatic source code generation that reduces the load on programmers and eliminates human errors. Charon also offers support for working with text in multiple languages, with easy loading and unloading of translated text.
With Charon, game developers can focus on creating engaging gameplay experiences without worrying about the technical details of managing game data. It is available in three deployment variants, including a standalone/offline application, web application, Unity and Unreal Engine plugins.
What is Charon
It is a .NET 4.6 console application that can be used as a command-line tool for performing CRUD operations with your game data, or as an HTTP Server to provide a UI for modeling and editing your game data. There are plugins for Unity and Unreal Engine that provide a more integrated experience while using Charon.
As with any .NET application, it can be launched as is on Windows and via Mono on macOS and Linux.
How it works
You create an empty gamedata.json
file when launching the Charon.exe application, which acts as an HTTP server. You edit your game data in the UI, then generate source code for your game engine. With this source code, you load gamedata.json
into your game and use it in a safe and structured manner.
<img width="894" alt="scheme" src="https://raw.githubusercontent.com/gamedevware/charon/main/docs/assets/how_it_works.png"/>
If you use plugins for Unity or Unreal Engine, it is a little bit easier than shown in the diagram.
Editor's UI
<img width="894" alt="screenshot" src="https://raw.githubusercontent.com/gamedevware/charon/main/docs/assets/editor_screenshot.png"/>
C# Code Example
using System.IO;
using var fileStream = File.OpenRead("gamedata.json"); // or .gdjs
var gameData = new GameData(fileStream, new Formatters.GameDataLoadOptions { Format = Formatters.Format.Json });
var heroes = gameData.Heroes.AsList // -> IReadOnlyList<Hero>
// or
var heroById = gameData.AllHeroes.Find("Arbalest"); // -> Hero | null
C++ Code Example
#include "UGameData.h"
TSoftObjectPtr<UGameData> GameDataPtr = TEXT("/Game/Content/GameData");
auto GameData = GameDataPtr.LoadSynchronous(); // -> UGameData*
auto Heroes = GameData->Heroes; // -> TMap<FString,UHero*>
auto HeroById = GameData->Heroes.Find(TEXT("Arbalest")); // -> UHero**
TypeScript Code Example
import { GameData } from './game.data';
import { Formatters } from './formatters';
// Node.js
import { readFileSync } from 'fs';
const gameDataStream = readFileSync(gameDataFilePath);
// Blob or File
const gameDataStream = gameDataFileBlob.arrayBuffer();
// XMLHttpRequest (XHR)
// gameDataRequest.responseType -> "arraybuffer"
const gameDataStream = gameDataRequest.response;
const gameData = new GameData(gameDataStream, {
format: Formatters.GameDataFormat.Json
});
let heroes = gameData.heroes; // -> readonly Hero[]
let hero = gameData.heroesAll.find("Arbalest"); // -> Hero | undefined
Haxe Code Example
import GameData;
import Formatters;
import haxe.io.Path;
sys.io.File;
var input = File.read("RpgGameData.gdjs"); // or .json
var options = new GameDataLoadOptions();
options.format = GameDataFormat.Json;
var gameData = new GameData(input, options);
var allHeroes = gameData.heroesAll.list // -> ReadOnlyArray<Hero>
var heroById = gameData.heroesAll.get("Arbalest"); // -> Hero
License
- Generated Code - MIT
- Plugins:
- Unreal Engine - MIT
- Unity - Unity Asset Store License
- Charon - CC BY-ND - can freely use and can redistribute, as long as it is passed along unchanged and in whole.
Product | Versions Compatible and additional computed target framework versions. |
---|---|
.NET Framework | net472 is compatible. net48 was computed. net481 was computed. |
-
.NETFramework 4.7.2
- No dependencies.
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.
Version | Downloads | Last updated |
---|---|---|
2024.3.6 | 214 | 10/18/2024 |
2024.3.4 | 175 | 10/2/2024 |
2024.2.22 | 138 | 7/9/2024 |
2024.2.18 | 177 | 7/1/2024 |
2024.2.6 | 127 | 6/11/2024 |
2024.2.5 | 107 | 6/10/2024 |
2024.1.13 | 315 | 5/6/2024 |
2024.1.6 | 429 | 3/3/2024 |
2024.1.4 | 260 | 2/20/2024 |
2024.1.1 | 251 | 1/15/2024 |
2024.1.0 | 231 | 1/4/2024 |
2023.4.22 | 255 | 12/13/2023 |
2023.4.16 | 251 | 11/14/2023 |
2023.4.14 | 326 | 10/30/2023 |
2023.4.4 | 311 | 10/15/2023 |
2023.4.1 | 235 | 10/5/2023 |
2023.4.0 | 247 | 10/3/2023 |
2020.1.1 | 2,157 | 3/1/2020 |
2020.1.0 | 612 | 1/22/2020 |
2019.4.3 | 584 | 12/23/2019 |
2019.3.10 | 622 | 11/12/2019 |
2019.3.9 | 585 | 10/28/2019 |
2019.3.8 | 591 | 10/8/2019 |
2019.3.5 | 617 | 9/15/2019 |
2019.3.1 | 991 | 7/22/2019 |
2019.2.3 | 1,176 | 5/5/2019 |
2019.2.0 | 628 | 4/24/2019 |
# 2024.3.6
## Game Data Editing
- Enhanced the Logical data type parser to accept "1" and "0" values during XLSX import.
- Fixed an issue in the Reference Repairer where referenced document IDs were not updated if they were in an unexpected format (e.g., a string instead of an integer).
- Resolved formatting errors in XLSX files that occurred when opening them in MS Excel.
- Fixed an XLIFF import error caused by a missing XLIFF version during deserialization.
- Corrected the OPTIONS request to files, ensuring that `Allow` headers are properly returned instead of an error.
- Fixed language mix-ups during export due to incorrect language lookup logic, which particularly affected XLIFF source and target languages.
- Prevented non-localizable columns from being included during exports performed using the DATA I18N EXPORT command or the Export Text option in the UI.
- Updated the `SafeUpdate` import mode to preserve document IDs, ensuring document structure and identity remain unchanged.
## User Interface
- Added tooltips for document reference fields to display extra-long reference names.
## CLI
- Fixed an issue where the DATA EXPORT command failed to export XLSX files due to an error.