Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Deathfly]

3.0.0 alpha-9

- Compatible to StarSector 0.95a.
- Fixed a CSV file decoding issue, which cause single quotation mark and line-breaker-in-comment result unintended phrasing.

https://github.com/Deathfly/sf-ship-ed/releases/download/3.0.0/sf-ship-ed.3.0.0-alpha-9.exe

[Üstad]

I tried to change the vigilance's missile hard point to a high arc turret. But it didn't work, can anyone help me about this?

Spoiler

   "shieldRadius": 80,
    "spriteName": "graphics/ships/vigilance.png",
    "style": "MIDLINE",
    "viewOffset": 0,
    "weaponSlots": [
        {
            "angle": 60,
            "arc": 270,
            "id": "WS 001",
            "locations": [
                13,
                14
            ],
            "mount": "TURRET",
            "size": "MEDIUM",
            "type": "ENERGY"
        },
        {
            "angle": 0,
            "arc": 105,
            "id": "WS 002",
            "locations": [
                41,
                -13
            ],
            "mount": "TURRET",
            "size": "MEDIUM",
            "type": "MISSILE"
        }
    ],
    "width": 63
}

[close]

[Wolfynator]

Unless I'm missing something, editing built-in wings does not seem to work.

[IonDragonX]

Unless I'm missing something, editing built-in wings does not seem to work.

Did you remember to give the ship_data.csv entry any bays?

[Wolfynator]

Unless I'm missing something, editing built-in wings does not seem to work.

Did you remember to give the ship_data.csv entry any bays?

Ok I solved it, I thought it was 'left arrow key' to remove a built-in wing and not 'backspace' lol. On an unrelated note, do you happen to know if .ship files get merged/replaced entirely? For some context, I have replaced the built-in wing of the shepherd with my own fighter, but the shepherd still retains the old borer wing and the new one is simply added.

[IonDragonX]

Ok I solved it, I thought it was 'left arrow key' to remove a built-in wing and not 'backspace' lol. On an unrelated note, do you happen to know if .ship files get merged/replaced entirely? For some context, I have replaced the built-in wing of the shepherd with my own fighter, but the shepherd still retains the old borer wing and the new one is simply added.

Yes, vanilla content is loaded by default. Your mod has created a new shepherd.ship file that is being added to the vanilla one. Since the vanilla has Borers, the sum says it still has Borers, you see?

If your shepherd.ship file correctly defines a whole ship, you can use the 'replace' command in your mod_info.json file.
  "replace":["data\\hulls\\shepherd.ship"],
The replace command stops the vanilla game from loading the target file. It TRUSTS that you are supplying a correct replacement because there are dependencies upon that file. (ie if it aint right, you crash)

[Wolfynator]

Ok I solved it, I thought it was 'left arrow key' to remove a built-in wing and not 'backspace' lol. On an unrelated note, do you happen to know if .ship files get merged/replaced entirely? For some context, I have replaced the built-in wing of the shepherd with my own fighter, but the shepherd still retains the old borer wing and the new one is simply added.

Yes, vanilla content is loaded by default. Your mod has created a new shepherd.ship file that is being added to the vanilla one. Since the vanilla has Borers, the sum says it still has Borers, you see?

If your shepherd.ship file correctly defines a whole ship, you can use the 'replace' command in your mod_info.json file.
  "replace":["data\\hulls\\shepherd.ship"],
The replace command stops the vanilla game from loading the target file. It TRUSTS that you are supplying a correct replacement because there are dependencies upon that file. (ie if it aint right, you crash)

Thanks, that was really helpful. Looks like I'm better off not replacing the vanilla shepherd and instead whip up a new one to avoid compatibility issues in the future.

[Üstad]

Ok I solved it, I thought it was 'left arrow key' to remove a built-in wing and not 'backspace' lol. On an unrelated note, do you happen to know if .ship files get merged/replaced entirely? For some context, I have replaced the built-in wing of the shepherd with my own fighter, but the shepherd still retains the old borer wing and the new one is simply added.

Yes, vanilla content is loaded by default. Your mod has created a new shepherd.ship file that is being added to the vanilla one. Since the vanilla has Borers, the sum says it still has Borers, you see?

If your shepherd.ship file correctly defines a whole ship, you can use the 'replace' command in your mod_info.json file.
  "replace":["data\\hulls\\shepherd.ship"],
The replace command stops the vanilla game from loading the target file. It TRUSTS that you are supplying a correct replacement because there are dependencies upon that file. (ie if it aint right, you crash)

It works for me as well but we didn't use to need to do this, not sure if the 0.95 update caused this. Is there any way around to implement our changes without the replace command in mod_info.json file?

[IonDragonX]

Ok I solved it, I thought it was 'left arrow key' to remove a built-in wing and not 'backspace' lol. On an unrelated note, do you happen to know if .ship files get merged/replaced entirely? For some context, I have replaced the built-in wing of the shepherd with my own fighter, but the shepherd still retains the old borer wing and the new one is simply added.

Yes, vanilla content is loaded by default. Your mod has created a new shepherd.ship file that is being added to the vanilla one. Since the vanilla has Borers, the sum says it still has Borers, you see?

If your shepherd.ship file correctly defines a whole ship, you can use the 'replace' command in your mod_info.json file.
  "replace":["data\\hulls\\shepherd.ship"],
The replace command stops the vanilla game from loading the target file. It TRUSTS that you are supplying a correct replacement because there are dependencies upon that file. (ie if it aint right, you crash)

It works for me as well but we didn't use to need to do this, not sure if the 0.95 update caused this. Is there any way around to implement our changes without the replace command in mod_info.json file?

Well, most mods just leave the Vanilla files alone and create new ships. If you make your mod use a different internal ID for your ship (EX: instead of "shepherd" you make "shepherd_ustad") then both versions of the ship would be in the game and not conflict.

[Üstad]

Is this only for ships? Because when I edit weapons the changes I made take place in the game.

[IonDragonX]

Is this only for ships? Because when I edit weapons the changes I made take place in the game.

Well, ships are actually *.variant in the campaign. When a new ship "pops" in campaign, the *.ship file has to be loaded first, the optional *.skin file is loaded second, and the *.variant is loaded last.
So, making a ship, skin, or variant file needs to be clean. Vanilla has already loaded its own information, so your changes are additive.
You are probably only changing values in the weapons_info.csv, maybe? Those changes will overwrite the vanilla csv file in every line with an identical ID name. Only new ID names are additive in a csv file.

[Üstad]

Is this only for ships? Because when I edit weapons the changes I made take place in the game.

Well, ships are actually *.variant in the campaign. When a new ship "pops" in campaign, the *.ship file has to be loaded first, the optional *.skin file is loaded second, and the *.variant is loaded last.
So, making a ship, skin, or variant file needs to be clean. Vanilla has already loaded its own information, so your changes are additive.
You are probably only changing values in the weapons_info.csv, maybe? Those changes will overwrite the vanilla csv file in every line with an identical ID name. Only new ID names are additive in a csv file.

I change some things about .wpn files as well such as "mountTypeOverride":"HYBRID", thing. When I change it without replace command the changes take part in the game.

[IonDragonX]

3.0.0 alpha-9

- Compatible to StarSector 0.95a.
- Fixed a CSV file decoding issue, which cause single quotation mark and line-breaker-in-comment result unintended phrasing.

https://github.com/Deathfly/sf-ship-ed/releases/download/3.0.0/sf-ship-ed.3.0.0-alpha-9.exe

In the variant mode, could you increase the weapon groups to 7? Would be nice.

[Deathfly]

3.0.0 alpha-10

-Rework weapon render order sorting to correctly follow hull render hints and weapon slot renderOrderMod.
-Add a notification to tell current hull do not have fighter bay when trying to add fighter wing on it.
-Raise weapon group limit to 7.
-Rework weapon mount icons so make them more easy to be precisely placed.

https://github.com/Deathfly/sf-ship-ed/releases/download/3.0.0/sf-ship-ed.3.0.0-alpha-10.exe

[BreenBB]

Interesting, its possible to change weapon slot types in ship mode?

Also about features, I think handy one is writing how much weapon slots of which size and type and fighters slots already have, and how much them is not build in, for more easier counting of them on big ships with alot of slots.