Crymson

you get no resources from harvesting your own ship, it is possible to get upgrades but you will hafta do it all manually this is all part of the new rebuild token system.

or maybe ask a modder to add it, assuming the data is in the LUA it should be simple.

I am fairly certain you cannot touch the block attributes as those are not exposed to LUA

yeah after doin some research I'm working on implementing this as a mod, should show up on the workshop soonish.

One of the things I like about Avorion is the procedurally generated nature of the game and its challenges. That said while there is alot of room to grow with faction interactions and such I would like to propose a simple but significant upgrade to the endgame gameplay.

Well assuming turret slots were no longer related to system module slots that would free up alot of room that would otherwise be taken by turret control modules. If the Turret bases each "used up" some processing power it would make it a dynamic of compensating processor use by turret slots against adding processing power to the ship to compensate. Also there would be fall off point as ships grow beyond a maximum size to processing power ratio where gains in size and processing power would outpace the need for system module slots and all that excess processing power could be diverted into turret deployment. Most of my argument for reworking turret allowances is focused on availability of turrets beyond what the 15 system slots allow for very large ships. At that point nothing natively existing in the game poses such ships a challenge. The challenge then becomes allowing those who wish to deploy such ships to do so in a fashion that remains relevant "within" the gameplay loop. It is easy enough to install a mod that provides modules with massive turret allowances and thus obviate this discussion altogether. I am trying to propose a solution that would keep these choices functionally important within the game design.

Currently turrets are tied to the essentially hardcapped system module slots. I can understand that decision but in a truly sandbox game this is rather restrictive for ship design. Virtually all other ship design elements can be controlled and scaled up as you increase ship size. Assembly, cloning, fighter cap, torpedo cap, academy, shields, power, all these scale directly with the ship and can be controlled with great granularity in the ship design. Turrets do not scale endlessly no matter how you build the ship. Here is my suggestion. 1) Require turrets to be mounted to turret bases. 2) Require more base volume not just face size for larger turrets. 3) Tie turret base volume to a ship power/processing power cost reflecting power feeds, capacitors, ammo feeds etc. 4) Make the costs for the turret bases scale so the more total volume of turret bases you have the greater the overall cost becomes in an exponential or logarithmic fashion. Possibly with an inverse power cost versus processing cost for larger vs smaller turret bases allowing the player to tinker with how they chose to arm ships as they get larger and larger. Perhaps turret bases could even reduce the overall processing power of a ship thus forcing players to make important choices between more guns or more module slots for upgrades, thus keeping that element of current gameplay intact. In this fashion you could build an over-gunned small ship or the Executor Class Super Star Destroyer with its hundreds of turbolaser batteries, it would all be a matter of building your ship to handle the requirements to power/feed the gun turrets. And when you get down to it one of the greatest glories of Avorion is ship design.

Hi, I like this mod quite a bit and want to use it on my dedicated server. However it is not available on the workshop and I only use workshop mods on my server for ease of pushing updates to my players. I also had to update this rather significantly to make it work in the current version of the game. That being said I am going to publish this to the workshop with full credits to you. If you do not want this on the workshop I will happily take it down just let me know. Thanks again for making this excellent mod.

if you simply set the Dependancy to {id = "Avorion", max = "0.*"} it will be compatible with any version of Avorion going forward. Personally when I create mods for any game I simply keep them up to date so the versioning doesn't become an issue. When I do decide to take a hiatus from modding on a game I will set a version limit if available, and I always note in the description what version the mod is made for and that it is no longer being maintained. Setting an arbitrary version limit on my mods when they will most likely continue to function regardless of game updates and especially the idea that they would become non functional beyond the next update seems like a really bad idea.

Literally every outdated mod, simply changing the version dependency in the modinfo.lua for the mod is enough to allow the game to load without issue. This is easy enough to do clientside for an individual but it literally stonewalled my dedicated server totally making it unplayable. I have done a workaround for now by publishing a small compilation mod of just the most crucial outdated mods for my gaming community. Client Log attached. Also attaching the server log from my dedicated server. clientlog_2019-08-08_04-25-44.txt serverlog_2019-08-07_15-59-01.txt

With 25.2 out there is a new problem with outdated mods. Now the system will not allow you to play with these mods even if you force enable them. I have even pulled some of these mods and installed them locally with the game version dependency set to 0.* and they load and function just fine. This affects both SP and MP servers, the game runs fine but when it tries to connect to the server whether dedicated or even the SP local server it errors out with "Error while enabling Mods:". This happens whether I am starting a new game or loading an existing game.