nerodestination.blogg.se - Starsector game window too small

#STARSECTOR GAME WINDOW TOO SMALL HOW TO#
#STARSECTOR GAME WINDOW TOO SMALL INSTALL#
#STARSECTOR GAME WINDOW TOO SMALL CODE#
#STARSECTOR GAME WINDOW TOO SMALL LICENSE#

Generally speaking, the process most people recommend for creating a ship sprite is:.

I'm not going to give a whole treatise on the artistry of making ship sprites (at least partially because I'm not great at it myself) but some important points to remember and useful resources are: PNG file with a transparent background, saved at 72 pixels/inch (not necessary, but helpful) and in 8 bits per channel color (absolutely necessary), with as little extra 'blank space' around the ship as possible.

The first thing you're going to need is a ship sprite. Later, we'll make a custom ship system, hullmod, and weapons for it, but for now it'll just be a ship.

#STARSECTOR GAME WINDOW TOO SMALL HOW TO#

That's probably what you wanted to learn how to mod to do anyway, right? I bet it was.įor the purposes of this tutorial, we're going to be creating a little shuttle called the Bastard, with a small missile hardpoint and a universal turret. Now that we've created a mod, let's make that mod actually do something! Specifically, let's make it add a custom ship to the game. It appears in the mod list and you can select it and run Starsector with it enabled! It won't do anything yet, of course, but we've taken the first step. And that's it! Congratulations, you're done! You've made a mod! Save that file in Starsector/mods/mymod (or whatever you named your mod folder). Opening up a mod_info.json from an existing mod, it should look something like this: The easiest way to get a working one is to copy it from another mod so let's go ahead and do that - mod_info JSONs aren't the sort of thing where you have to worry about intellectual property. Once we've done that, we're going to need a mod_info.json file - this is a JSON formatted text file that tells the game that the mod exists. For this tutorial, we're going to call it 'My Mod'.

#STARSECTOR GAME WINDOW TOO SMALL INSTALL#

Navigate to your Starsector install directory, open the /mods/ subfolder, and create a new folder - title it whatever you want the name of your mod to be. So, the first thing we need to do is literally create the mod.

7.5 Campaign Spawning (also required for Custom Production from Colonies).

4 Custom Blueprint and Manufacturer/Tech Type.

2.6 Campaign Spawning (also required for Custom Production from Colonies).

Once we've got those together, we're ready to start working on our mod. There are several tutorials on the forums on how to set up your preferred IDE for Starsector modding:

Eventually, (you do NOT need to set up an IDE for making a basic ship or weapon!) an IDE for editing scripts and compiling a.

Many people use Krita or GIMP (which are free) to good effect.

An art program that supports transparency layers: Adobe Photoshop is industry standard, but expensive.

#STARSECTOR GAME WINDOW TOO SMALL LICENSE#

csv files: If you have a license for Microsoft Excel you can use that (as long as your language is set to US English or else it saves wrong), otherwise I recommend downloading the free Ron's CSV Editor. Notepad++ is lightweight, blazing fast, and Windows-only, but lacks some useful features, such as json validation.

#STARSECTOR GAME WINDOW TOO SMALL CODE#

VS Code is cross-platform and full-featured, with thousands of extensions.

The Notepad program that comes with Windows is bad and you shouldn't use it. By the end of this tutorial, you will have a mod with a custom ship, weapon, faction, star system, and associated other creations, as well as a passing familiarity with the concepts and processes involved in implementing these.įirst, lets go over what we're gonna need: The purpose of this tutorial is to create sort of a 'minimum viable product' when it comes to modding - a simple mod including all of the facets that normally come to mind when one thinks of a Starsector mod.