mirror of
https://github.com/Expand-sys/CCash
synced 2025-12-16 16:12:14 +11:00
30 lines
1.7 KiB
Markdown
30 lines
1.7 KiB
Markdown
[PREVIOUS PAGE](../README.md) | [NEXT PAGE](connected_services/how_to/explanation.md)
|
|
|
|
CCash is an external ledger for in-game economies, running on a webserver with a RESTful API, exceptionally fast and lightweight written in C++.
|
|
|
|
While CCash can be used for anything that can interact with its API I think minecraft is a good usecase.
|
|
|
|
The currency model most Minecraft Servers adopt if any, is resource based, usually diamonds. This model is fraught with issues however:
|
|
|
|
* The primary issue is minecraft worlds are infinite, leading to hyper inflation as everyone accrues more diamonds.
|
|
* Some resources are passively reapable (e.g iron or gold), making the generation of currency a larger focus than that of creating value.
|
|
* Locality is required for transactions.
|
|
* Theft is possible; ownership is physical possession based.
|
|
|
|
CCash solves these issues and adds a level of abstraction. The main philosophy of CCash is to have fast core operations which other services build on, CCash can proccess thousands of requests per second.
|
|
|
|
The CCash instance can be external to the game server:
|
|
|
|
|
|
|
|
Or on localhost:
|
|
|
|
|
|
|
|
Running it local to the game server reduces latency for connected services and CCash is very lightweight and so will be a tiny proportion of the server's total computation.
|
|
|
|
**DISCLAIMER: ComputerCraft requires you add `127.0.0.1` to its config section `allowed_domains` if you're interacting with CCash locally**
|
|
|
|
As CCash is just a means of keeping track of who has what, the economic system you use is entirely up to whomever hosts the instance.
|
|
|
|
I suggest an admin should manage the instance to lower incentive to manipulate balances.
|