I don't use Vortex for X4, since it didn't work at the beginning. Just dump the content of your archive into your extensions folder. I think, the problem was something with the file and folder rights, because X4 expects mods in D:\Steam\steamapps\common\X4 Foundations\extensions (Or your Steam Path) and not in your home directory. I agree with Nexus, it would be better the other way, but well, Egosoft decided differently on this one.
hello and thank you for this mod. question please, if i remove or rename the jobs.xml in the extensions\stardust\libraries folder would that be enough to prevent the game from spawning stardust for argon fleets? i'm wanting only player access to stardust. disregard, answered my own question, and renaming jobs.xml is apparently enough to do what i wanted. thanks again for the mod.
well it appears that egosoft has borked this mod with release 6.0, can't install engines, guns, etc. here's hoping you are able to find time to update the mod, really miss not being able to build any now.
Hiho, well, to make it short: I found a major bug in the stardust. There is stardust in X4, and the ship did conflict with it, because I internally named it also stardust. My bad, for not checking before, that this was a conflict. It kinda worked with old releases, but not with 5.0 anymore. Yes, it is compatible with 5.x. Also older versions might work, unless you start a new game. I recommend using the last version, since the conflict was solved. The last version doubles the power of the canons. Cheers, Keeshah.
please make sure to use the last version, 1.4. Also make sure it is installed not in your home but here: Steam\SteamApps\common\X4 Foundations\extensions. The Colossus itself didn't change, under XL there should be now a new ship, called Stardust. Please tell me, if you got along with those hints.
Cheers, Kee.
P.S.: I myself had problems, too, but only with the packed version. Go figure, please use the Version 1.5 and tell me, if that works better. But still, it needs to be in {x4Steamhome}\extensions and not your home.
Installed the mod 1.71 using Vortex: the ship did not appear in the choice box of argon shipyard in spite of the message that the mod was installed when started the game. Also blueprints of stardust and the stardust weapon appeared at reps office. I bought the blueprints but did not have an option to craft on my own yard. Solution ---- manually transferred files of 1.7 version to the extension folder and everything started working. Either it is the mod version or Vortex (used a lot for other mods and normally I did not have problems with it). X4 game - English version 3.0+ on steam
"For vro version ship must have the lgun hgun tag for each weapon or turret and make an internal shield generator because shields in vro are very tiny and work like a little bonus in capacity & regen"...also hgun are much strongher than lgun so keep game balance in mind. To make ship work with VRO, not only guns but internal shield need to be edited. Elite Augmented VRO mod is good example how to add it to your ships and allow them to be used by AI. https://www.nexusmods.com/x4foundations/mods/461
You know, the internal shield puts me in a weird position. I don't use VRO and probably never will use it, since it does change the gameplay completely to something different and is a huge change of the original game. This means, I can't test this properly. And a lot of my mods have additional shields, for some of them it is the only change, besides stat edits. So if I support those internal shields, how do I test them? They don't work in the regular game, at least this is, what I was told. Play a new game up to test VRO? The guns are not a problem, she shields are. BTW, that lgun/hgun thing lies in the players responsibility, since those are mainly playerships. So, now you might see my problem, I just don't know, how to make my mods vro compatible.
76 comments
"The installer stardust.zip-302-4-01-1734739677.zip is invalid and couldn't be installed: content.xml invalid: invalid attribute name
Line:1
Column:112
Char: 2
"
Or just use the E Version? then it would be well rounded!. and VRO semes good.
Will you take a look at that?
hello and thank you for this mod. question please, if i remove or rename the jobs.xml in the extensions\stardust\libraries folder would that be enough to prevent the game from spawning stardust for argon fleets? i'm wanting only player access to stardust.disregard, answered my own question, and renaming jobs.xml is apparently enough to do what i wanted. thanks again for the mod.
Could you, please, update the changelog and post what exactly was fixed/changed in 2.20/2.21?
Is 2.10 still compatible with X4 v5?
Thank you so much in advance.
well, to make it short: I found a major bug in the stardust. There is stardust in X4, and the ship did conflict with it, because I internally named it also stardust. My bad, for not checking before, that this was a conflict. It kinda worked with old releases, but not with 5.0 anymore.
Yes, it is compatible with 5.x.
Also older versions might work, unless you start a new game. I recommend using the last version, since the conflict was solved.
The last version doubles the power of the canons.
Cheers,
Keeshah.
please make sure to use the last version, 1.4.
Also make sure it is installed not in your home but here: Steam\SteamApps\common\X4 Foundations\extensions.
The Colossus itself didn't change, under XL there should be now a new ship, called Stardust.
Please tell me, if you got along with those hints.
Cheers,
Kee.
P.S.: I myself had problems, too, but only with the packed version. Go figure, please use the Version 1.5 and tell me, if that works better. But still, it needs to be in {x4Steamhome}\extensions and not your home.
Solution ---- manually transferred files of 1.7 version to the extension folder and everything started working. Either it is the mod version or Vortex (used a lot for other mods and normally I did not have problems with it).
X4 game - English version 3.0+ on steam
To make ship work with VRO, not only guns but internal shield need to be edited.
Elite Augmented VRO mod is good example how to add it to your ships and allow them to be used by AI.
https://www.nexusmods.com/x4foundations/mods/461
I don't use VRO and probably never will use it, since it does change the gameplay completely to something different and is a huge change of the original game. This means, I can't test this properly. And a lot of my mods have additional shields, for some of them it is the only change, besides stat edits.
So if I support those internal shields, how do I test them? They don't work in the regular game, at least this is, what I was told.
Play a new game up to test VRO? The guns are not a problem, she shields are.
BTW, that lgun/hgun thing lies in the players responsibility, since those are mainly playerships.
So, now you might see my problem, I just don't know, how to make my mods vro compatible.