DEVS! I FOUND THE FIX FOR TURRET FACTORY DAMAGE BUG!

[_OMAR_]

HI GUYS!!

 

I AM very EXCITED!

 

This annoying bug since the beginning that glitches the damage and other stuff of certain turrets at turret factory when you increase the amount of goods and expecting a better stats instead its going rock bottom or even to minus! I found the FIX!!!

 

I checked the turretfactory.lua and noticed that those SPECIFIC turrets and specific goods have some MISSING lines at coding. I simply replaced the missing parst by copy pasting from unbugged turrets  and "guest" the values for them and it FIXED!

 

Originally it was like this

 

 

elseif weaponType == WeaponType.Laser then

        return {

            {name = "Laser Head",          amount = 2,    investable = 4,  minimum = 1, weaponStat = "damage", investFactor = 2.0, },

            {name = "Laser Compressor",    amount = 2,    investable = 3,              weaponStat = "damage", investFactor = 2.0, },

            {name = "High Capacity Lens",  amount = 2,    investable = 4,              weaponStat = "reach", investFactor = 2.0, },

            {name = "Laser Modulator",      amount = 2,    investable = 4,              turretStat = "energyIncreasePerSecond", investFactor = -0.2, changeType = StatChanges.Percentage },

            {name = "Steel",                amount = 5,    investable = 10, minimum = 3,},

            {name = "Crystal",              amount = 2,    investable = 10, minimum = 1,},

            {name = "Targeting System",    amount = 0,    investable = 2, minimum = 0, turretStat = "automatic", investFactor = 1, changeType = StatChanges.Flat},

        }

 

 

And this is what i did

 

  elseif weaponType == WeaponType.Laser then

        return {

          {name = "Laser Head",          amount = 2,    investable = 4,  minimum = 1,  rarityFactor = 0.75, weaponStat = "damage", investFactor = 0.2,changeType = StatChanges.Percentage  },

            {name = "Laser Compressor",    amount = 2,    investable = 3, minimum = 1,  weaponStat = "damage", investFactor = 0.2, changeType = StatChanges.Percentage  },

            {name = "High Capacity Lens",  amount = 2,    investable = 4,  minimum = 1,  weaponStat = "reach", investFactor = 0.2, changeType = StatChanges.Percentage },

            {name = "Laser Modulator",      amount = 2,    investable = 4,  minimum = 1, turretStat = "energyIncreasePerSecond", investFactor = -0.2, changeType = StatChanges.Percentage },

            {name = "Steel",                amount = 5,    investable = 10, minimum = 3,},

            {name = "Crystal",              amount = 2,    investable = 10, minimum = 1,},

            {name = "Targeting System",    amount = 0,    investable = 2, minimum = 0, turretStat = "automatic", investFactor = 1, changeType = StatChanges.Flat},

        }

 

 

 

I have no idea if i put too high or low value because me no dev or anything but point is this made the turret factory work proper again!

 

So DEVS PLEASE put this in the game ASAP!

 

I put the modified turretfactory.lua in the attachment. Can download and put it in \Steam\steamapps\common\Avorion\data\scripts\entity\merchants folder and play one less bug!!! ( Version 0,15,7 r10230)

 

THANK YOU!

 

... Man i am happy, and excited... Shaking a bit too for no reason ;D

 

Editted: The "investFactor = 0.2" this number was 2.0 which was brokenly op or no damage when deacreased the amount. Obviously right number was 0,2 not 2,0 ;D! Sorry for mistake ... Told you I am no dev or anything

 

Edit2: Worked on it little more and now launchers and salvage turrets mining turrets are also working normal turretfactory.lua has been updated you can simply copy paste it to your game's C:\Program Files (x86)\Steam\steamapps\common\Avorion\data\scripts\entity\merchants

file and play (version 1.5.230).

turretfactory.zip

[Devious]

Thank you for looking into it, weve tried looking into it aswell but didnt notice this before.

Will see if the values are allright when Im home so we can throw it on our server.

[_OMAR_]

Thank you very much! I would love to see this fixed in the next update.

[Shrooblord]

Wow, cool. Updating my own turretfactory.lua as we speak. Thank you for sharing this!

[Raith]

I disagree with this solution. If you pay attention to the code, the omitted values are just uninitialized (aka zero). (I previously was working under the assumption that values were inherited from a previous ingredient during generation. I assumed that rarityFactor was introduced only in the first ingredient for that reason. But that does not give me an answer to what the default investFactor - is it 1? But I digress.)

 

For example: StatChange - has 3 values, all of which are used in the calculations later; the default would be 0 and only changed to 1 or 2 where needed - exactly what the dev did. If you also pay close attention to the calculations of price and materials, those are scaled back and forth, so for example setting a minimum value to 1 (from default 0) changes the price.

 

I am confident that the dev had good reasons (balance reasons) for choosing these values and formulas. When you just randomly plug "missing" values of one bugged turret with another turret's data... you might aswell be just making it worse, since you're basically fiddling with balancing of the game and not addressing the actual bug (imo). These bugs are in the code that calculates, if it works for some turrets, it means there are edge cases where it does not handle the values correctly. The values themselves are hardly an issue. I can concede only that StatChange type could be wrong for certain things - say it should be 1 (percent) instead of 0 (default). But you really need to test out all possible scenarios before you claim you have a solution.

 

Edit: for me personally the affected turrets are only Launchers (range decreases instead of increasing) and Railguns/Lightning guns (damage decreases instead of inreasing) of EXCEPTIONAL quality, common/uncommon/rare are however unaffected. Go figure. Also only in one random turret factory, the 4 other I checked work fine (as intended). The changes proposed here however would affect all turrect factories, hardly addressing the underlying issues.

[_OMAR_]

I am no coder nor dev. I just did my best to help the devs get rid of very annoying bug. Yes what i did was ruined the balance but by working on it little more i managed to put numbers right. To me its going to negative numbers or insanely high is a 'bug' and right now I am playing the game without it nor any op gun. You are right about disagreeing this fix because intention of it is address this bug to developers in a different way that they might miss it before...

Thank you.

[Kamo]

Yup, that's what we beta-testers have to do. Since part of the game code is open to us, it's probably okay to help the devs code. I mean, they have so much things to do on their side, with the rest of the game code :) !

The finetuning and rebalancing'll have to be made for later, when the whole shebang's gonna be overhauled, better procedural ship generation, HP, volume and DPS intervals, dynamic and multivariable difficulty, economy equilibrium, product sinking and faction ship production (economy based on built and not spawned from nothing ships), etc.

[Shrooblord]

Oh, yey, I've been quoted not once, nor twice, nay thrice! I feel honoured ^^~*

 

Raith, I'm curious, you claim this fix will break Turret Factories in a lot of other places. Have you any data on that by any chance? I'd love to learn how this change introduces more breakage than it solves. Maybe we can learn from that and try and fix that, too.

[_OMAR_]

I updated the file. I highly suggest you to redownload it.

 

Thank you

[Shrooblord]

What did you change?

[_OMAR_]

Mining and salvage laser damage and ranges were weird. Either too far away or literally nothing. Fixed that one and also launchers warhead stuff was getting wonky if it had a damage buff fixed that too and a bit more balancing on tesla and laser so those are not 7k dps at max anymore or minus at lowest. Also cannon turret damage is fixed as well. Some turret factories are fine but with certain buffs glitches getting appeared so as i discover them, i am fixing them. That's why its getting updated. Please have Awesome fun with your custom turrets like mine!

Thank you

[Raith]

Oh, yey, I've been quoted not once, nor twice, nay thrice! I feel honoured ^^~*

 

Raith, I'm curious, you claim this fix will break Turret Factories in a lot of other places. Have you any data on that by any chance? I'd love to learn how this change introduces more breakage than it solves. Maybe we can learn from that and try and fix that, too.

 

I did not say it breaks other things, the proposed solution however hides the errors in the calculation code (for edge cases that dev did not forsee), which in turn might result in overpowered turrets at other factories that were working as intended and within certain min-max values. Handling of these edge cases should be included in the code, capping on one side insane growth of stats at some maximum to avoid OP turrets and on the other hand capping at a certain minimum that would otherwise decrease stats. Mind you all of the abose is speculation on my part, as I have not looked into exactly where the initial values for any stats come from.

 

I really only glanced at the code in the few critical places, I unfortunatelly did not perform an in depth analysis. I wonder if turret factories are created with a certain seed value, which dictates the stats of turrets. Whatever the generation code is, I am inclined to consider the calculation code broken rather than values that only affect balance. TBH balancing something should never result in completely unexpected results (aka decreasing stats). All energy saving (reducing) multipliers are negative, which implies that something should decrease only and only if the multiplier is negative. Something with a positive multiplier should only increase. If that's not the definition of unexpected behaviour then I don't know what is.

 

If anyone has info directly from the dev saying that the code is fine and the issue might be in the turret values (what I keep calling balance issues) - please correct me. Otherwise code that is fine, should not behave like that.

 

I have 5 turret factories, only one of them has weird behaviour. I'll repeat myself: only for 3 types of turrets and only for exceptional rarity - I believe this to be sufficient proof that you simply cannot fix this by balancing the turrets to your random liking.

 

I do not have any data as I did not bother flying around with these fixes on and off for multiple factories, but I might compite something if I'm not to lazy. Stay tuned.

 

EDIT: Some data. Sample size: anecdotal. Results: inconclusive. Changes applied to Launchers:

 

FROM:

{name = "High Pressure Tube", amount = 2, investable = 6, minimum = 1, weaponStat = "reach",},
{name = "Fuel", amount = 2, investable = 6, minimum = 1, weaponStat = "reach", investFactor = 0.5,},

 

TO:

{name = "High Pressure Tube", amount = 2, investable = 6, minimum = 1, weaponStat = "reach", investFactor = 0.5, changeType = StatChanges.Percentage,},
{name = "Fuel", amount = 2, investable = 6, minimum = 1, weaponStat = "reach", investFactor = 0.5, changeType = StatChanges.Percentage,},

 

Despite a few turret factories behaving weird before applying the proposed fixes, after applying them Launchers did not experience range decreasing, however range increasing two or even three times was very popular. Additionally one factory gave different initial range values. Riddle that one for me.

 

I don't know about you, but I don't like it. It is inconsistent across the board before and after, which only reinforces my belief that it's not the turret values but calculation (or some other) code.

[Shrooblord]

Mind you all of the abose is speculation on my part, as I have not looked into exactly where the initial values for any stats come from.

Ah, I see. This is what I was wondering about: you seemed rather adamant about your suggestion to first fix the root cause of the damage scaling, and cap it as you say, so I thought you may have some experience with super over-the-top powerful guns by introducing the changes proposed by others in this thread. I was only meaning to try and isolate where these insane damage scalings could be coming from so we could fix them, as you suggest, you see.

 

I wonder if turret factories are created with a certain seed value, which dictates the stats of turrets.

Yes they are and yes it does. Good thinking! There's a mod out there which adds a Seed box to Turret Factories much like how Shipyards have them for randomly generated ships.

 

Whatever the generation code is, I am inclined to consider the calculation code broken rather than values that only affect balance. TBH balancing something should never result in completely unexpected results (aka decreasing stats). All energy saving (reducing) multipliers are negative, which implies that something should decrease only and only if the multiplier is negative. Something with a positive multiplier should only increase. If that's not the definition of unexpected behaviour then I don't know what is.

Naturally. This is also why we consider this strange behaviour "a bug". ;)

I agree with you.

 

I have 5 turret factories, only one of them has weird behaviour. I'll repeat myself: only for 3 types of turrets and only for exceptional rarity - I believe this to be sufficient proof that you simply cannot fix this by balancing the turrets to your random liking.

Mkay, I'm starting to see where you're coming from. Sure, this could be a worthwhile venture to investigate how Turret generation is formulated, in order to try and squash the bug.

However, introducing a change in the code that gets rid of one bug should be good progress, right? That it doesn't solve a different bug isn't that change's fault. After all, we may not be talking about only one bug here that is affecting Turret damage across the board, but rather a number of factors that are all contributing to faulty damage calculations.

 

Despite a few turret factories behaving weird before applying the proposed fixes, after applying them Launchers did not experience range decreasing, however range increasing two or even three times was very popular. Additionally one factory gave different initial range values. Riddle that one for me.

Very strange. Keep in mind though that most of the entities in the game do not expect to have their internal code changed after they've been spawned. New entities should work "fine" with new code, but existing ones may behave in unexpected manners, due to their initial spawning setting them up with a different range of values and stats than what the new code they're using at run-time is expecting them to have.

 

But let me repeat my previous point. The bug is: when you add items that cost money to invest into making a Turret, stats that are universally considered better when they improve go down, literally making it so that investing no extra materials or even scrapping materials from the Turret to make it cheaper than default actually causes its stats to get buffed. This doesn't make any sense, correct?

The changes introduced by OP fixes that issue, making the behaviour follow common sense: you want a better Turret, you invest more materials. You want a cheaper Turret, by investing less materials? Sure, but you're gonna end up with a crappier Turret. That's expected behaviour, wouldn't you say so?

 

So the changes introduced are a bug fix. Isn't that healthy progress?

 

I don't know about you, but I don't like it. It is inconsistent across the board before and after, which only reinforces my belief that it's not the turret values but calculation (or some other) code.

I agree, but I'd like to reiterate that these could definitely be not one bug causing the issue, but rather two or a multitude of them multiplying down the code blocks and giving you the end result of confusing damage calculations.

 

I feel like we need to investigate more in order to properly answer this, but my main argument in this whole discussion will be and stay: OP introduces a bug fix. Less bugs means more stable game and happier gamer, who experiences a game that follows expected behaviour. Correct? If so, cool! Let's try to now focus on the remaining bugs, like the damage calculation being off and inconsistent. If not, please do speak up. Let's talk.

[Raith]

Lets agree to disagree, I personally have been tweaking turretfacroty.lua since maybe 0.12 or was it 0.14... the point is I did not consider this a good bugfix back then so I never suggested it, that's why I am arguing against it now. It's only a temporary band aid at best, that ensures you have no illogical behaviour for the time being. It's perfect for that.

 

Note that I am not the only one editing turretfactory.lua for such a long time, here's a topic from Feb 4 2017, almost a year ago. The solution (un)fortunately did not get any traction back then and I believe it should not get right now, since it is basically the same.

 

Problem is a few missing line in the turretfactory.lua as i seen....

 

Its between line 79 and 87, minimum = 1 and the changeType = StatChanges.Percentage part. i already fix it for my self just to copy it to the other 3 line below, if you take a look on the other turrets you will se how its need to be look like.

 

The author is working under the identical faulty assumption that some code is missing. I'll concede that game version changed, it got developed further, but the bug remains and in my opinion this is still no the fix we're looking for.

 

So back to the current topic, tweaking positive values gives you both negative and positive results (but you expected only positive), that's not right at all, there's some threshold where it rolls over into negative and is not handled. Say you edit turret values, how are you now supposed to find this unhandled edge case which used to produce negative results? You've just successfully hid a bug, which is gonna come back once you start balancing the game.

 

I would really love to take apart the three cases of StatChanges (it will likely require going deeper) and actually see what is happening to the numbers, maybe then I could gain more insight into the issue and have stronger arguments against this fix. I'll try to do this (soon™).

 

Yes they are and yes it does. Good thinking! There's a mod out there which adds a Seed box to Turret Factories much like how Shipyards have them for randomly generated ships.

 

Thanks, I might have actually seen this, but never used it.

 

After all, we may not be talking about only one bug here that is affecting Turret damage across the board, but rather a number of factors that are all contributing to faulty damage calculations.

 

Indeed, however before applying the suggested changes I would like the OP to give more justification for them (good data, bigger sample, some deeper understanding of the code) rather than working under a false assumption that the values are "missing", they're not, they're set to default (0, 1, whatever default is). And if you're already poking in the code, look for other factors. It is highly likely the issue is caused by multiple factors, that's why I refuse to accept a solution that addresses only one aspect (turret values). I might be demanding too much, but the solution should be complex (multiple edits addressing different parts of the code, even if one of those things are turret values). In all honesty turret values should be only responsible for balance and despite the fact that I stressed it before I understand that balance is not that high of a priority in an actively developed game that still has such bugs.

 

I would like to leave it at "agree to disagree", until the dev (directly or through someone else) can verify this (turret values specifically) has not been looked into already and if it is at all a valid path to pursue or not. Because I have my doubts.

 

PS: [meta] why is the burden of proof on me? lol. Don't get me wrong, I love debating. But why do I have to argue and gather data to disprove a fix, which is clearly based on speculation. Please grill the OP for this purpose :D

[Shrooblord]

So back to the current topic, tweaking positive values gives you both negative and positive results (but you expected only positive), that's not right at all, there's some threshold where it rolls over into negative and is not handled. Say you edit turret values, how are you now supposed to find this unhandled edge case which used to produce negative results? You've just successfully hid a bug, which is gonna come back once you start balancing the game.

Now I get you. So we have to find out how to get the Math to reveal when the numbers roll over. Is this an out-of-bounds indexing problem, I wonder?

 

How does a bonus "just" roll over like that?

 

Ah, or is the in-game code working with some percentage Math that is flopping out, like much of the game does? You know, how we used to be able to get -100% Shield Charging = instant recharge when not being hit nonsense (not sure if that's been patched, actually)?

 

Do you have any idea how to start investigating this, since you've had prior experience to messing with turretfactory.lua?

 

Reading the rest of the post, it would appear you and I agree on this speculation (faulty percentage / factorisation Math causing issues).

 

Re:P.S.: I didn't really mean to put a burden of proof on you, nor argue vehemently against you; I know I may come across as such as I am rather verbose in discourse, and I like to elaborate a lot to make myself as clear as possible. I'm mostly interested in how you figured that the proposed fix is "simply wrong", specifically because initially you didn't seem to explain why you think so, yourself, in clear language that came across to me. Maybe that's my fault. It just seemed to me like you were saying something along the lines of "you think you fixed it but you didn't, though I'm not saying why exactly / I don't know specifically but it just seems that way to me". I concede, that's a major point of projection on my part - I apologise. It also appears you have more experience in the matter than I first gathered, which is all I was really asking for in the first place; if you say that what seems a simple bug to fix isn't what it seems, I'm intrigued and inquisitive as to why, mostly so that we can try and track the root of the bug down ourselves, in order to either A) let the dev know where it is so they can fix it or B) fix it ourselves using mods until the dev does so, too.

That's why I may seem a little pushy to get more information out of you. I've worked as a QA Tester for over a year and I'm a scientist by field of study, and at heart; I've gotten very much into the mindset of "Something goes wrong, but why? Give me data and let's analyse."

[_OMAR_]

The values were acting completely vice versa when there's certain buffs on some turret factories (damage). So I added some lines that says something about set percentage and such. This made it go as expected ways, like if you put more you get more or if you put less you get less. But still numbers were off. Why? Because you CAN'T find a gun in xanion quality that does 7k dps or 3k dmg per hit. Also SAME guns were dealing LITERALLY minus damages just because you put 5 less goodies. I said ok those numbers needs fixing. I tested... Not put numbers on my head but tested! If it goes minus then we need to decrease the percentage of the investfactor right? Who wants a canon which has only 2k range? Do you find any so far in the game other than building it with this 'bug'? So i dropped the numbers. Also WHY all other perfectly working fine weapons has those CERTAIN lines on them when some specific ones don't which is the irony the ones having such issues? I always kept an eye on the other weapons coding. For example you could build a tesla turret at 8k dps at max and minus 2k at min. Interestingly that invest factor on the tesla damage was 3.0 when every other weapon is 0.2 or 0.3 0.75 max! Then guess what? After putting the number down to 0.2 "just like others" it had 1.5k max "best case" which is very possible to find such gun and 500 min.

 

I am not a good programmer nor anything but so far this much i could do for a really annoying 'bug' for me. Without stating it as an ultimate must have thing or anything. After all we are trying to help the devs here. So its very possible that my way is not the right one but for now its A way and if you have a better solution to this instead of living with the bug till devs fix it please feel free to share it...

[Raith]

Ah' date=' or is the in-game code working with some percentage Math that is flopping out, like much of the game does? You know, how we used to be able to get -100% Shield Charging = instant recharge when not being hit nonsense (not sure if that's been patched, actually)?[/quote']

 

Sounds fun, have not seen/experienced it, but I'm relatively new to the game (0.12++).

 

Do you have any idea how to start investigating this, since you've had prior experience to messing with turretfactory.lua?

 

Reading the rest of the post, it would appear you and I agree on this speculation (faulty percentage / factorisation Math causing issues).

 

Excellent. I am glad I got my point across. That's why I was stressing that we should look at the formula that calculates stats, but that's hard to do on our end (ideally you'd use a debugger and follow the code, even then it might not be as simple as that). Generalizing, it's just investigate the code, in fact it might span more than just turretfactory.lua (speculating here). I guess what we can realisticly do is just simulate the calculations, for that you must figure out the parts of the code that calculate the stats and/or where do they come from in the first place (ie.: defaults). Something along those lines. Then prepare an excel sheet (or program) and play with the numbers, it would still be much more efficient than loading the game after every single change. If you simulate every step of the calculation you might see where exactly it all goes off the rails - investigate that.

 

We also need comprehensive tests on the weapons generated with shorter than expected range and zero/negative damage - are they performing as the tooltip says? I would hate to waste my time digging into how stats are calculated only to discover everything is kosher in that department. That means that for example the bug could be only "visual", in the representation of the numbers, in the tooltip or something, which is a completely different file. I personally have not experimented with these bugged weapons so I have no data to support or refute the ideas I put forward. I however have seen posts form the dev (maybe this was fixed) that for some weapons (asume lasers, miners, salvagers or so) had their laser beams go way too far or not far enough in comparison with the reticle, but they were functioning properly and it was only visual. I have no clue if this is worth looking into as well.

 

I do not do lua. lua (like python) variables have no types declared and that triggers me... and complicates code readability. I do not know how much time I can invest into this, I'd love to make a contribution, but it's coming soon™.

[Shrooblord]

Actually you talking about the dev talking about weapons triggered a bit of a light bulb in my head. It could very well be that these are all bugs that are already being focused on by the devs and will be resolved during the combat update, whenever that hits. It would be so so useful if we could get some feedback on that front.

 

So perhaps it's only a matter of waiting til the next update... worth a "shot"?

 

Alternatively, I can suggest to you a method of rapid code iteration that doesn't require you to boot/reboot or quit/reload an Avorion game every time you make a change, if you're not adverse to "cheating".

 

[*]Head into an empty Sector you don't care about. This will be our playground to test things in.

[*]Attach the Entity Debugger to your ship by selecting your ship and entering /run Entity():addScript("lib/entitydbg.lua")

into Chat.

[*]Use the Entity Debugger to spawn an instance of the Turret Factory (for example).

[*]Change something in code.

[*]Destroy the old Turret Factory by selecting it and typing /destroy in Chat (be mindful you don't accidentally select your own ship, or this could get ugly). This will create a lot of gibs over time, so be careful. Spawn a new Turret Factory. Your new code is applied to it even though you never reloaded the game!

 

Protip: Copy-Paste, and the up and down arrow keys are both valid inputs for the Chat window, and will help you a bunch with (re)typing commands.

[Raith]

Actually you talking about the dev talking about weapons triggered a bit of a light bulb in my head. It could very well be that these are all bugs that are already being focused on by the devs and will be resolved during the combat update, whenever that hits. It would be so so useful if we could get some feedback on that front.

 

So perhaps it's only a matter of waiting til the next update... worth a "shot"?

 

Alternatively, I can suggest to you a method of rapid code iteration that doesn't require you to boot/reboot or quit/reload an Avorion game every time you make a change, if you're not adverse to "cheating".

 

[*]Head into an empty Sector you don't care about. This will be our playground to test things in.

[*]Attach the Entity Debugger to your ship by selecting your ship and entering /run Entity():addScript("lib/entitydbg.lua")

into Chat.

[*]Use the Entity Debugger to spawn an instance of the Turret Factory (for example).

[*]Change something in code.

[*]Destroy the old Turret Factory by selecting it and typing /destroy in Chat (be mindful you don't accidentally select your own ship, or this could get ugly). This will create a lot of gibs over time, so be careful. Spawn a new Turret Factory. Your new code is applied to it even though you never reloaded the game!

 

Protip: Copy-Paste, and the up and down arrow keys are both valid inputs for the Chat window, and will help you a bunch with (re)typing commands.

 

Thanks, I'll have to check out what debug info is avalable and how verbose it is. I'm not sure that I'd see every step of the calculation thought, so I might still need to fall back on just simulating the calculation in excel or whatever, however this should be excellent for live testing of edits to the code.

 

I do agree that even a tiny amount of feedback from the dev would go a long way, especially if you keep in mind that the combat update is already being in the works and is the next planned update. That slipped my mind cimpletely, even thought I read the steam News as soon as they're out :D

[Shrooblord]

The entitydbg.lua script is actually not what you think: it's not a debugger tool that follows your scripts and reports back. Instead, it's mostly a "cheat window" where you can spawn/summon a bunch of stuff like ships, trigger events to start (eg. Pirate Attack / Alien Invasion), add cargo to your hold, spawn a new Station of any type you choose, and even spawn in / generate whole Sectors.

[bobisback]

@_OMAR_ Good work on this! Can I put this into a mod I am about to release?

[_OMAR_]

Of course! Feel free to modify and use as you see fit!