building:devsite
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
|
building:devsite [2019/03/27 15:37] Mavrixio |
building:devsite [2019/03/27 16:16] Mavrixio |
||
|---|---|---|---|
| Line 35: | Line 35: | ||
| - Server Access Control: You can control which server can have access (load) the resources from a speficic ERF. | - Server Access Control: You can control which server can have access (load) the resources from a speficic ERF. | ||
| - Areas Visibility in the DM Client: The DM client only lists areas that are from ERFs with the "Show Areas in the DM Client" setting activated. | - Areas Visibility in the DM Client: The DM client only lists areas that are from ERFs with the "Show Areas in the DM Client" setting activated. | ||
| - | - ERFs are used to sort: log entries, [[.:devsite#resources_revsion_system|resources backup]], loot tables, custom factions and weathers | + | - ERFs are used to sort: log entries, [[.:devsite#resources_revision_system|resources backup]], loot tables, custom factions and weathers |
| - | + | ||
| + | ===== ERFs / Resources Prefix ===== | ||
| + | The prefix is the part of the ResRef / Blueprint that is **before** the **first** undercore. For exampl: | ||
| + | ^Full ResRef^Extracted Prefix^ | ||
| + | |agn_area_001|agn| | ||
| + | |test___001|test| | ||
| + | |0_1_2_3|0_| | ||
| + | |_abcd|| | ||
| + | It it used to determine from which ERF a resource come from and from there (the ERF) the server can know the remaining (which server / who has access, what weather to use...) | ||
| + | \\ \\ | ||
| + | ERFs have one main prefix and can have secondary prefixs (but secondary prefixes are not recommended). | ||
| ===== Resources Revision System ===== | ===== Resources Revision System ===== | ||
| - | Sinfar development system uses Git under the hood. Each ERF has their own folder and the folder containing all those ERF folders is a Git repository: \\ | + | Sinfar development system uses Git under the hood. Everytime that you: |
| + | * Edit a resources from the website (compile a script, save a dialog or 2da or GFF resource) | ||
| + | * Upload resources into an ERF | ||
| + | * Rebuild an ERF | ||
| + | A commit is created with all changes and pushed into the Git repository. So **all changes can be tracked and reverted**. | ||
| + | |||
| + | ==== Git Repository Structure (For Advance Users) ==== | ||
| + | Each ERF has their own folder and the folder containing all those ERF folders is a Git repository: \\ | ||
| {{:building:devsite_20190327-113115.png}} \\ | {{:building:devsite_20190327-113115.png}} \\ | ||
| \\ | \\ | ||
| GFF resources (*.ut?, *.ifo, *.are and *.git) are stored in a JSON format, for example: | GFF resources (*.ut?, *.ifo, *.are and *.git) are stored in a JSON format, for example: | ||
| <code> | <code> | ||
| - | |||
| [ | [ | ||
| 4294967295, | 4294967295, | ||
| Line 61: | Line 78: | ||
| } | } | ||
| ], | ], | ||
| - | ... | + | ... |
| </code> | </code> | ||
| + | Sot it possible (but far from perfect...) for the system to merge, revert and display changes. GFF resources have the extra extension .json added to them: \\ | ||
| + | {{:building:devsite_20190327-114109.png}} \\ | ||
| + | Remmber that this is only for the Git repository, the game server doesn't understand this JSON format. The game server load the resources from a clone of the repository that has the binary (GFF) format of the resources. | ||
building/devsite.txt · Last modified: 2019/03/27 16:20 by Mavrixio