Mirror/Erupe
1
0
Fork 0
mirror of https://github.com/Mezeporta/Erupe.git synced 2026-03-21 23:22:34 +01:00
Code Issues Packages Projects Releases Wiki Activity

docs(md): minor review of the markdown files.

Browse Source
This commit is contained in:
Houmgaor
2025-09-10 00:19:46 +02:00
parent 531b3d2fa6
commit 1268a77712
2 changed files with 29 additions and 18 deletions
Download Patch File Download Diff File Expand all files Collapse all files

32
AUTHORS.md
View File

@@ -1,30 +1,36 @@
# List of authors who contributed to Erupe
## Point of current development
The project is currently developed under https://github.com/ZeruLight/Erupe
The project is currently developed under <https://github.com/ZeruLight/Erupe>
## History of development
Development of this project dates back to 2019, and was developed under various umbrellas over time:
* Cappuccino (Fist/Ando/Ellie42) ("The Erupe Developers"), 2019-2020 (https://github.com/Ellie42/Erupe / https://github.com/ricochhet/Erupe-Legacy) (Still active closed source)
* Cappuccino (Fist/Ando/Ellie42) ("The Erupe Developers"), 2019-2020 (<https://github.com/Ellie42/Erupe> / <https://github.com/ricochhet/Erupe-Legacy>) (Still active closed source)
* Einherjar Team, ????-2022 Feb (There is no git history for this period, this team's work was taken and used as a foundation for future repositories)
* Community Edition, 2022 (https://github.com/xl3lackout/Erupe)
* sekaiwish Fork, 2022 (https://github.com/sekaiwish/Erupe)
* ZeruLight, 2022-2023 (https://github.com/ZeruLight/Erupe)
* Community Edition, 2022 (<https://github.com/xl3lackout/Erupe>)
* sekaiwish Fork, 2022 (<https://github.com/sekaiwish/Erupe>)
* ZeruLight, 2022-2023 (<https://github.com/ZeruLight/Erupe>)
## Authorship of the code
Authorship is assigned for each commit within the git history, which is stored in these git repos:
* https://github.com/ZeruLight/Erupe
* https://github.com/Ellie42/Erupe
* https://github.com/ricochhet/Erupe-Legacy
* https://github.com/xl3lackout/Erupe
Note the divergence between Ellie42's branch and xl3lackout's where history has been lost.
Authorship is assigned for each commit within the git history, which is stored in these git repos:
* <https://github.com/ZeruLight/Erupe>
* <https://github.com/Ellie42/Erupe>
* <https://github.com/ricochhet/Erupe-Legacy>
* <https://github.com/xl3lackout/Erupe>
Note the divergence between Ellie42's branch and xl3lackout's where history has been lost.
Unfortunately, we have no detailed information on the history of Erupe before 2022.
If somebody can provide information, please contact us, so that we can make this history available.
If somebody can provide information, please contact us, so that we can make this history available.
## Exceptions with third-party libraries
The third-party libraries have their own way of addressing authorship and the authorship of commits importing/updating
a third-party library reflects who did the importing instead of who wrote the code within the commit.
The authors of third-party libraries are not explicitly mentioned, and usually is possible to obtain from the files belonging to the third-party libraries.
The authors of third-party libraries are not explicitly mentioned, and usually is possible to obtain from the files belonging to the third-party libraries.

15
README.md
View File

@@ -1,12 +1,16 @@
# Erupe
## Client Compatibility
### Platforms
- PC
- PlayStation 3
- PlayStation Vita
- Wii U (Up to Z2)
### Versions (ClientMode)
- All versions after HR compression (G10-ZZ) have been tested extensively and have great functionality.
- All versions available on Wii U (G3-Z2) have been tested and should have good functionality.
- The second oldest found version is Forward.4 (FW.4), this version has basic functionality.
@@ -34,17 +38,18 @@ If you want to modify or compile Erupe yourself, please read on.
## Docker
Please see [docker/README.md](./docker/README.md). This is intended for quick installs and development, not for production.
Please see [docker/README.md](./docker/README.md). This is intended for quick installs and development, not for production.
## Schemas
## Schemas
We source control the following schemas:
We source control the following schemas:
- Initialization Schema: This initializes the application database to a specific version (9.1.0).
- Update Schemas: These are update files that should be ran on top of the initialization schema.
- Patch Schemas: These are for development and should be run after running all initialization and update schema. These get condensed into `Update Schemas` and deleted when updated to a new release.
- Bundled Schemas: These are demo reference files to give servers standard set-ups.
- Bundled Schemas: These are demo reference files to give servers standard set-ups.
Note: Patch schemas are subject to change! You should only be using them if you are following along with development.
Note: Patch schemas are subject to change! You should only be using them if you are following along with development.
## Resources