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 well know how this game can be a lot funnier when modded, so ask me freely :)
I added a link with my notes about all the changes i made to the game for better help you and all the folks who love modding :)
I add it here too just because:
https://drive.google.com/file/d/1pgHlqRgi60e8ZDKlDAKbSQZtqqJ28nxX/view?usp=sharing
Also, do you know how to mod the .exe file like the fan mod does? Seems like all the juicy stuff like psionics mechanics is in there and i want to modify some of that.
VIDEO LINK:
https://drive.google.com/file/d/1EkLtoDBAEhmXfJf2Qv5QnrwC1GTJoH5w/view?usp=sharing
About modding the .exe file the matter is a bit more tricky.
Roughly 2 years ago i happened to have this conversation with... An user, who i thought a comrade Modder:
This Statement:
"It's because it involves accessing their source code which is their intellectual property that I can't share it with people without Kerberos' consent. That would be illegal."
Makes me think i may have problems sharing publicly here how to mod the .exe file. Although I have not documented myself about the matter so it may be a ♥♥♥♥♥♥♥♥ (probably it is).
But as the saying goes: "Better safe than sorry". so for now i'll avoid to share how to mod the .exe file here for avoid an eventual retaliate from kerberos (Mecron in particular).
Anyway. If you or someone else will send me a friend request, i may accept it and then something after that may will happens... Who Knows :)
P. S.
The same "Illegal" thing may apply to unpacking the .XNB files too but since this discussion is still up. There are 2 possibilities:
1) Kerberos is tolerant (Mecron tolerant?)
2) The guide is fine.
Well... Draw your conclusions :)
So, what would be the difference between that and what you want to create exactly?
edit: lets put it this way i'm so noob i only found out about the pit inifity 2 days ago so now i'm super exited for covid-19 to go away so that once i got a job again i can get myself it
Strange.
If you add “Equipment: [Item_ID]” to the starting items list of a character, it should work with any item (weapons included).
E.G.
Directory: C:\#SOTS_TP_Modding_Tools\Unpacked_Files\dlc\02_jnaut\data\d02.txt
Mercenary VANILLA Starting Items list
Feel free to provide me with more information so that i can eventually better help you.
On the subject, i'm confident that the ID and naming is correct as i've Ctrl-C/Ctrl-V'ed them from their respective lists. Considering the process worked for other weapons i've added i'm certain i copied the correct field too.
But i've since discovered that adding said weapon to another character works perfectly. So the current solution is to do gunrunning with them to the next blue locker and continue from there.
For context, i tried to add the Heavy Machine Gun to Striker, the game CTD'ed seconds after start. but when i added it to the Scout, it was perfectly fine. perhaps it has something to do with the weapon's race origin? I've not tested this with every weapon, but most weapon with Morrigi origins works fine while the Human ones doesn't.
Maybe i could try the reverse, adding Crow guns to the original three and see what happens.
This is the crash report:
So i think that your guess about the crash having something to do with the weapon's race origin is correct.
A trick i found to “solve” your issue was to mod the “race” of the problematic weapon to “none”