Print

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

[Dark.Revenant]

Does the 'Expanded Flight Decks' percentage bonus also apply to wings being rebuilt, or is it just for re-arming?

It applies to both.

[Schwartz]

Pretty cool mod. In effect it doubles flight decks (or very nearly anyway, depending on how it adds up with skills), but it's still a mixed blessing thanks to OP cost.

Possible bug: I noticed it can't be installed on Shadowyards' Charybdis carrier.

[Dark.Revenant]

Only dedicated carriers (ships with the Carrier tag) count for that hullmod.  I should update that to be available for all ships with flight decks, I suppose.

[orost]

Remember my complaints about extra UI elements such as the leading pip and the Priwen Burst indicator not working? I noticed something that might be useful in tracking it down: it works in missions, but not in campaign. Additionally, after loading a campaign game, it will stop working in missions too until the game is restarted. Obviously I can only test the Priwen Burst in missions, not the pip, but so far I've always seen them behave identically.

Also, I've had an opportunity to play Starsector on a PC with Windows and a dedicated graphics card with 1 GB memory and it does the same thing, to put to rest worries about Linux or insufficient video memory being the culprit.

edit: I updated all my mods to make sure it hasn't been fixed recently, and the Templar burst now works as designed in campaign and in missions, but the pip still doesn't. Confusion abounds.

[sotanaht]

Please make a note of the current incompatibility between Nexerelin and Exigency in the first post.  Attempting to run them both WILL crash the game.  I think people are going through the original post here and downloading everything you recommend without really looking too closely at each mod.

[Tartiflette]

The incompatibility with Nexerelin is already mentioned in the Nexerelin thread, as it should. There is no reason for having it in the SS+ thread since it doesn't concern this mod.

[MesoTroniK]

The update of Exigency will be done soon™, would be sooner but some stuff keeps getting in the way of it going smoothly...

[sotanaht]

The incompatibility with Nexerelin is already mentioned in the Nexerelin thread, as it should. There is no reason for having it in the SS+ thread since it doesn't concern this mod.

I know it's mentioned there, but if someone goes down the list and downloads everything here, they get a crash.  Then they have to track down the source of the crash.  It happened to me, I had to check my log file, noticed that Exigency was mentioned every time, and was able to track down the conflict from there.  Apparently I'm already smarter than the average forumer, since the Nexerelin thread has a debug help request that turns out to be the Exigency incompatibility almost every page.  I think it would help cut down on that sort of headache, and a little bit of redundancy doesn't hurt.

But I guess I'm not the one who has to help people troubleshoot, and I've already figured out the problem myself, so what's it matter to me right?

[Thaago]

Hi DR, just started a game. The combat aptitude tooltip seems bugged - the "Reduces Deployment Cost by" is saying 3% with 2 aptitude points spent. I checked with both 1 and 2 points spent and the actual effect seems fine, its just the tooltip.

[orost]

Some comments on starting options:

In the Lasher + Vigilance option, the Vigilance is almost completely useless. After the speed nerf, Pilums do nothing against small ships (which is what the player will be fighting early), and the short-ranged Heavy Burst Laser forces it to close in, which is suicidal for such a fragile ship. I'd give it a Salamander pod and a Graviton Beam instead, and replace the Salamanders on the Lasher with Annihilators.

The Enforcer start is horrifically difficult, since the Enforcer is such a weak solo ship. How about a Vanguard instead? A bit more powerful, and definitely more interesting to fly. I'd arm it with a Mk IX and a mix of assault guns and machine guns.

edit: Maybe also put in a Camel somewhere? It's a very nice ship that I feel most players probably overlook.

[Tommy]

The Enforcer start is horrifically difficult, since the Enforcer is such a weak solo ship.

Actually, the Enforcer is a powerhouse solo ship. Strap 2 flak cannons on the sides, one Needler and 2 maulers and you're a god.

[orost]

How do you manage to avoid getting swarmed? I've tried a loadout like this, with longer-range weapons, but I just get rushed by frigates, and once they're close I have neither the shields nor the armor to survive very long. Flak Running with burn drive only gets you so far and is a bit at odds with actually shotting things.

[Schwartz]

I run a similar loadout with 2 Dual Flak, 2 Mauler, 1 HVD and 4 Annihilator Rockets (for large enemies and to flux-stress PD). The key here is to use your range and put pressure on the first frigate quickly. The sooner you can even the odds the better, because a typical Enforcer loadout will mostly rely on shields to tank incoming torpedoes that it can't dodge. For SS+ I've used the no-shield mod on Enfos and Dominators successfully, though I'm always a bit wary sending them into combat with no way to emergency-tank a Reaper.

Even so, know your limits. If you're not a heavy Combat build, then chances are you'll want some support if the number of frigates going after you is just too high. HVD and Mauler don't really get any weaker in close-range engagements, there you just have less accurate alternatives with a slight edge in DPS, but nothing substantial.

[Histidine]

...wait, you talk about Enforcers getting swarmed under by frigates and then ask for a Vanguard instead? o_O what

[orost]

Disregarding burn drive (which I dislike and find mostly unhelpful, although that's maybe my incompetence), the Vanguard is faster and more maneuverable, and has the burst damage to very quickly pop a frigate that gets too close. I've had more luck with it than with an Enforcer.