Post by Deleted on Jan 20, 2019 15:42:57 GMT 10
Hello, friends!
I want to discuss the challenges of external libraries.
This may allow you to expand the capabilities of the engine.
What is the use of calls to external libraries?
1.Interception of api functions.
2.Implementation of its functions.
3.Extension of existing functions.
The engine is designed as a library startup file that calls these methods from the game folder, such as sounds. If you remove the UPX packer from the engine, you can find calls to scripts and other files.
Implementations
1.Write a dynamic library, compose functions, make api interaction with other libraries.
2.If you are writing a library to extend the functionality of the engine, you need to comply with all the features of its work, including loading and unloading. Because the engine interacts with each level of the game.
3.Optimization, at least to reduce the code of your library, because the engine can heavily load the system, or even hang.
An example of such a function is obvious, take the END Series.
I was able to get snow in the game, it falls in the street, and does not fall in buildings. The library is called at the entrance of the building, when the music changes automatically, my library turns on.
It will be convenient to write your own library and pack it into a dat file, then call it through the engine.
If this method does not suit you, you can inject into the memory of the game, with subsequent replacement of bytes. This method is not universal, but, it is simple.
I want to discuss the challenges of external libraries.
This may allow you to expand the capabilities of the engine.
What is the use of calls to external libraries?
1.Interception of api functions.
2.Implementation of its functions.
3.Extension of existing functions.
The engine is designed as a library startup file that calls these methods from the game folder, such as sounds. If you remove the UPX packer from the engine, you can find calls to scripts and other files.
Implementations
1.Write a dynamic library, compose functions, make api interaction with other libraries.
2.If you are writing a library to extend the functionality of the engine, you need to comply with all the features of its work, including loading and unloading. Because the engine interacts with each level of the game.
3.Optimization, at least to reduce the code of your library, because the engine can heavily load the system, or even hang.
An example of such a function is obvious, take the END Series.
I was able to get snow in the game, it falls in the street, and does not fall in buildings. The library is called at the entrance of the building, when the music changes automatically, my library turns on.
It will be convenient to write your own library and pack it into a dat file, then call it through the engine.
If this method does not suit you, you can inject into the memory of the game, with subsequent replacement of bytes. This method is not universal, but, it is simple.
