Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
I've been busy working on three mods, so I really don't have the time for these tasks right now.
But I can offer you some suggestions:
1. Modifying the DLL (C#) code of an existing mod is more difficult than creating a sub-mod.
2. You may need some basic knowledge of C# and XML.
3. Modifying the DLL (C#) code of an existing mod requires the use of Harmony. You can check out its tutorial here: https://harmony.pardeike.net/articles/intro.html
4. You'll need some decompilation software, such as ILSpy (https://github.com/icsharpcode/ILSpy), to view the source code of the original game and other mods.
5. Some of the core code for Vanilla Outposts Expanded is in the Vanilla Expanded Framework (Assemblies/Outposts.dll).
6. You can also check out the relevant public code for the Vanilla Expanded Framework on Github (https://github.com/Vanilla-Expanded).
Maybe you can also try making some suggestions to the members of the Vanilla Outposts Expanded development team. After all, it's much easier for them to modify the source code than it is for us.
Good luck!