Transport Fever 2

Transport Fever 2

Not enough ratings
h4e API
   
Award
Favorite
Favorited
Unfavorite
Misc: Script Mod
File Size
Posted
Updated
227.569 KB
22 Aug, 2024 @ 8:29pm
2 Sep, 2024 @ 5:11pm
15 Change Notes ( view )

Subscribe to download
h4e API

Description
h4e API

h4e API is a mod that provides various functions as a basis for other mods. For example, h4e API can be a prerequisite for installing a mod and using it successfully. In addition, this mod is also aimed at other modders who want to use the h4e API (e.g. h4e API as a prerequisite).

What can h4e API do for players?

The h4e API provides a similar basis to the Common API, for example, it ensures that the station can be built modularly with as many mod tracks as possible. However, there are still tracks that are currently not compatible, especially those that were written with other APIs and are designed for this, this must be tried individually. If there are any problems, please contact the person who created the track, it may be possible to solve the problem.

In addition, the h4eAPI provides various settings that can be changed via the Mod Manager in the game, including MANY values of the base_config.lua

What can h4e API do for modders?

It takes over data functions and provides data wherever it is needed. The API also ensures that stations can use tracks other than the vanilla tracks, and that very easily! But that's by far not all! The API has all repos except modelRep permanently on call, and the data is only loaded when it is actually called up, which saves performance in gameplay. Instead of dynamically entering the track in the EdgeList of the station in the module, every track is simply entered there right from the start, regardless of whether it is used.

Recommended contents

Popular Discussions View All (5)
0
2 Sep, 2024 @ 5:09pm
PINNED: Roadmap for h4e API
homieforever
0
28 Aug, 2024 @ 8:37am
PINNED: Settings
homieforever
0
26 Aug, 2024 @ 3:34pm
PINNED: Modding Documentation
homieforever
1 Comments
TheBackYard 30 Aug, 2024 @ 5:36am 
can this be combined with commonAPI2 or will it conflict?