Recent community posts
New build introduces weapon mods! Jump Mines, Flak Bursts, Drones and more!
This build brings weapon mods. When a shipyard creates a new weapon it'll have a chance to apply one of the applicable mods:
Pulse Weapons have Flak, an explosive pulse that can also destroy warheads easier, and Shotgun, multiple pulses for the charge of one!
Missiles have Cluster, which split into multiple warheads to avoid point defense, and Drone, which will circle your target and fire pulses at it.
Mines have Field Emitter, which fires a field weapon when the target gets near them, and Jump which will try to "jump" close to the target instead of being stationary and waiting for the target to come to them.
Starship Command 2
Starship Command 2 is a persistent-world, massively single-player, real-time tactical starship simulator wrapped in an AI-driven 4X game. Starting with a lowly shuttle, you will trade and battle your way to victory, amassing a gigantic fleet customized to your liking!
In the game the first thing you do is setup a galaxy. Then SsC2 will populate it with AI-controlled empires that play their own 4X (eXplore, eXpand, eXploit, and eXterminate) game. You play as a captain for one of these empires by trading commodities, completing missions, collecting taxes from sectors and battle the other empires for glory!
Massively single-player means that at any time you can switch between different captains of different empires in the same galaxy, playing both sides of a conflict.
Right now, to start a new game you need to go into the program directory and delete all the files (but NOT folders) in the "Data\Mods\Standard\Save" directory, or you could delete the entire save folder and add in the save folder "music", "images" and "images\hulls".
I haven't added a way in-game to clean the save folder, (there's still a lot to do!). If I have time in the next build I'll add a "reset game" button
If you want to setup a wiki for the game, that'd be great! You'd have my blessing. I don't have a way to set one up on my end right now. But if you do, you can see all the damage values, empire stats, etc. in the data folder.
Yeah, if you could download it straight from the site and see if it saves that way, that'd be great. I always forget about the Itch app, I need to test it on my end.
For the random closing, there should be a crash log in the games directory ( %APPDATA%\itch\apps\Starship Command 2\ for the Itch app) if there is one I could take a look at it.
Also, there are some settings that could be changed in the settings file, lowering the max number of empires should help, and lowering the max hull size<- that actually could be the source of the closing, with SsC2 making an image too large for your memory.
I could make a tweaked settings file for you, if you'd like.
I haven't made a manual yet. I've been planning to, but just haven't gotten around to it yet. I'd be happy to answer any questions in the meantime though.
The game should save automatically when you quit. If it's not that's a bug I need to fix. Could you tell me if you are running the game through the Itch App, or downloading it directly from the site and if so, where is the game unzipped? (It might be a permissions issue)
And yes! All empires will expand on their own even if you do nothing. In fact, if you are the galaxy view, you can press the F5 button and toggle a "watcher mode" which will let you set the time rate to 5000x and watch the empires expand and fight.
May I ask what kind of performance updates? I'm always trying to improve the performance, but if there is some specific areas that you noticed, It'd help to know.
There are some tips you can do to make SsC2 less demanding:
In the settings file:
- Change "combatLighting" to false.
- Lower "bumpStrength" to 0.
- Lower "maxEffectsCount" and "maxEffectsCountHardLimit" to a lower number, the first is a soft limit where it will start to cull older particles faster, and the second is a hard limit that will remove the oldest particles over this number.
- Change "particleShader" to false, this and the "maxEffect"'s settings will give you the biggest improvement in performance.
Those are the probably the best settings to change for increasing performance. Another tip would be to limit the size of your fleet, since SsC2 will try to match your fleet in strength, which can cause a massive battle of ships. I try to keep my fleet to ~20 ships, on my nine-year old Q9550.
Thanks. There should be a crash log in the game's directory. Could you either post it here or email it to me? It'd help trying to hunt down the bug.
If you are using the itch.io app, the crash log should be in %APPDATA%\itch\apps\Starship Command 2\
If you downloaded the game manually from the website the crash log will be in the root folder of wherever you extracted the zip.
Hey, I just whipped up a fix during breakfast. The new build (170527-0923) has an option in the settings file called "guiScale" that can be changed and it will resize the GUI accordingly.
The GUI is currently built around a 1280x720 screen, so for a 4k monitor (3840x2160) the guiScale option can be changed to a 3 to fit.
I haven't had the time to check it out very thoroughly (have to get to work) so there may be some small placement issues.
Hi! I don't have a resolution settings for text yet. But I went and made a mod for you to increase the font size. Just extract the files to \Data\Mods\Standard\GUI\panels\ and overwrite them. (If you're using the itch.io app the path should be %APPDATA%\itch\apps\Starship Command 2\Data\Mods\Standard\GUI\panels\)
It's a quick fix and probably won't look pretty, but it should get the job done until I put that feature in. I hope it helps!
P.S. 4k! I haven't tried it on a monitor with that resolution! I'd love to know how it works!
I just uploaded a new version that should log the reason for crashing. If you could try it and after a crash, post or email me the contents of %APPDATA%\itch\apps\Starship Command 2\crash.log I should be able to figure out why it's not working.
Hmm, thanks. That should be more than enough in specs. Can you tell me where the zip is extracted to? It may be a permissions issue or something similar. You could try extracting it straight to the C: drive and see if it works.