mirror of
https://github.com/Mezeporta/Erupe.git
synced 2026-03-22 23:54:33 +01:00
38d11fdabf
Mainly, there are differences in the MHFG low version network protocol when pkt.ShopType=1 or 2 in handleMgMhfEnumerationShop. Conducted code judgment and differentiation processing. If you need to configure the optional material list among the three options, Configure directly in gacha_detries The same Entry Type can be merged and displayed in GG In addition, the prizes are also directly configured in the gacha-entries table, MHFG1~GG does not use the gacha_items table throughout the entire process, which meets the lottery function of MHFG with a more single function In addition, the MHFG function itself is relatively simple Example of lottery configuration for G1~GG: eg: gachaname:test entry: itemgroup: group1:(choose one of the two) ITEM_1_ID:7 COUNT:1 ITEM_1_ID:8 COUNT:2 group2:ITEM_1_ID:9 COUNT:3 reward: reward1: ITEM_ID:1 COUNT:4 weight:10% reward1: ITEM_ID:2 COUNT:5 weight:90% table:gacha_shop |id|min_gr|min_hr|name|url_bannel|url_feature|url_thmubnail|wide|recommendded|gacha_type|hidden| |1|0|0|test|null|null|null|f|f|3|t| table:gacha_entries |id|gacha_id|entry_type|item_type|item_number|item_quantity|weight|rarity|rolls|frontier_points|daily_limit|name| |1|1|0|7|7|1|0|0|0|0|0|null| |4|1|0|7|8|2|0|0|0|0|0|null| |5|1|1|7|9|3|0|0|0|0|0|null| |8|1|100|7|1|4|1000|0|0|0|0|null| |9|1|100|7|2|5|9000|0|0|0|0|null|
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.
- The oldest found version is Season 6.0 (S6.0), however functionality is very limited.
If you have an installed copy of Monster Hunter Frontier on an old hard drive, please get in contact so we can archive it!
Setup
If you are only looking to install Erupe, please use a pre-compiled binary.
If you want to modify or compile Erupe yourself, please read on.
Requirements
Installation
- Bring up a fresh database by using the backup file attached with the latest release.
- Run each script under patch-schema as they introduce newer schema.
- Edit config.json such that the database password matches your PostgreSQL setup.
- Run
go buildorgo run .to compile Erupe.
Docker
Please see docker/README.md. This is intended for quick installs and development, not for production.
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 Schemasand deleted when updated to a new release. - 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.