Starsector 0.97a is out! (02/02/24); New blog post: Save/Load UI, Autosave, Intel Map Markers, and More (04/10/24)
No, .jpg does not support transparency so using it for something like ship sprites won't fly. In addition, file mass has *zero* impact on vram usage. It is purely based on the image canvas size.Awwh, that's a bit of a bummer too! I just managed to find out that a lot of the sprites as png could be lossy-compressed, but if it's canvas size only, the only thing that could be done is trimming the transparent edges (and I'm uncertain if that'll do much of a number on it.)CodeRound up width and height to a power of 2
Width * height
* 4 (24-bit depth with 8-bit alpha)
* 4 / 3 (mipmaps)
= Bytes
Another way to go about it would be to store reports of the yields from manufacturing and print out a notification, either weekly or as part of the monthly income report, perhaps?Ahh, dandy!Hmm, if it's the message spam that's getting to you, I suggest going to settings.json - you can enable and disable some of the notification settings for the forges there! An issue with weekly updates is that it opens up some options for cheese, i.e. only adding forge modules at the start of the week for the update, then removing it again. Daily updates coincide with many engine updates, such as ship maintenance, so it's better suited there.
Also, if i could make a suggestion, do you think you could make it so that the forgeships could proc every week, as opposed to every day? With the associated increase of production, that is, 7 days of work triggered once every 7 days. They're pretty awesome, but when travelling they really spam things up, due to the shortness of days.
Suggestion to suggestion:It might still be a good idea to track events if they have diplomatic implications, IE any expedition that loses you reputation if it fails without being bribed away.
Only real threats are shown on screen. If threat is minor (attackers outmatched by defenders) it is ignored and timer will not appear, only short message (as it is now).
It makes sense to track events only if they need player's personal participation.
Is this for a specific library version, or is the line out of date?
"name":"Nijigen Extend",
"author":"Created by creature.",
"version":"0.2.0",,
In the campaign, a ship's unmodified sensor strength and profile are the same and they are 30, 60, 90 and 150 for frigates, destroyers, cruisers and capital ships respectively. In combat, a bigger ship doesn't necessarily equal higher range, and it certainly doesn't say anything about firepower that guns on that ship don't say by itself, so it's not immediately necessary to know what size category a ship is. There are many modifiers at play when it comes to ship. For the player side ships, if you bought them, you should know it already from hullmods and/or sensor stats.It's worth noting that the only way you'll come to understand that sensor range strictly relates to hullsize ingame, is if you've noticed that all ships of an approximate hullsize both share a base sensor range and also that their hullmods all treat them as same-sized ships. Which is something you'd know via the hullmods.
By the way, recovering a ship and then scuttling it is equivalent to salvaging the ship immediately. It might make decision making when it comes to unknown ships a little easier.
