Hellsmith

The fix is pretty easy for the new patch: Go through the files of the mod and look for any line that says something like InvokeClientFunction("blablabla") Then search for the function with the name blablabla and add directly after it callable(nil, "blablabla") You do that for every invoke in every file and use the correct function names instead of blablabla and the mod works again.... I guess :D

Hey sorry guys, I have been quite buisy. But as soon as I figure out a good way to place turrets only on turret platforms for ships I will publish an new version and fix the other issues. I will also integrate a value into the config file that determines whether the model should be scalable or not. So that even in the start sector huge ships could exist. And therefore a difficulty rating for the factions in the config file is also necessary to prevent that. But again. I need to find the time for that and as I said, the code already looks like the devs intend that functionality already in the near future

Still not sure about a better place to put it :D 5. The command to send a ship somewhere lets the ship ignore void rifts. Even though the interface recognizes the barriers and displays the "available" sector range correctly you can simply send a ship somewhere within its circular range and the ship will jump. Never got that easy into the core ;-)

I don't know where to post beta branch issue feedback other than here. 1. If you change the ship orders of a ship that is currently mining to attack enemies in sector it will start to attack the currently mined asteroid. 2. Selling and buying remote order via the map won't work if you or another player aren't present in the system where the buy/sell orders are placed. 3. Big ships fail to mine even with only one miner on the ship. They seem to go to a distance equal to their bounding box length to the asteroid. Mining beams won't go that far

With the newest patch I also had errors when moving into sectors with planets. Maybe I missed a special use of the plangenerator there. I will look into it. About the torpedos I probably should have taken less detailed designs from the workshop. But as this mod is meant as a basis for you/the community to setup factions I hope this mod inspires people to build more CPU efficient designs ;) Or at least inspire the devs to an easy way to incorporate player made factions into the game. Best would to have the option to publish whole faction configs to the Steam Workshop

Hello fellow Space Captains, I have a small Mod for you. Using this you can replace NPC random block composed ships by those masterworks of people on the steam workshop. The mod was actually very easily applied and judging by the already available global functions supplied by Avorion this mod may be obsolete in the near future. How it works The supplied config file describes 3 factions. Every faction in the game will be assigned one "style" of those and every new ship or station that spawns for that faction will use one of the supplied workshop designs for that. There are some categories already that ships can apply to, like "Defender" NPC ships will be Cruiser and "Attacker" NPCs will be BattleShip. If a faction config does not supply a version for a category, the default ship will be used. And if that also fails the block generator of Avorion will be used. How to install Simply extract the content of the supplied ZIP file to the directory of Avorion. Overwrite the files in the script folder when requested. The default I supply you with works with a handy and small Steam Workshop Collection: https://steamcommunity.com/sharedfiles/filedetails/?id=1524022688 How you can use your own collection or another will be explained. How to install on a server Pretty much the same except that I have no clue how to download Workshop files on a dedicated server other than manually uploading them ;) You can basically put them anywhere on your server file system and change the config.lua accordingly. But I've found it to be convenient to test the faction client side first and then put everything on the server. Therefore use the Steam Standard structure and copy your steam workshop folder content in the same structure to the server: steam/steamapps/workshop/content/445220/[ships here] How to edit it In the folder "mods/factionships" you will find a file called config.lua. This file contains the configuration for NPC factions and what workshop ships it should use. The default content is composed of 3 factions. If you add or remove a new faction section make sure to set the FactionCount property in the top of the file accordingly. To get the right files and the Steam Workshop entries you can go through all the ships/stations you want to use in Steam and add entry ID to the config. You can find the Workshop entry ID in the top of your steam window. The folder on your filesystem has the same name. Be careful to look whether the file in the folder is called plan.xml. I encountered files called design.xml. Known Issues - Adding a new faction mid-game will most likely end up mixing styles for existing factions. The faction styles are as of now applied by the faction index property. - Some ship categories of pirates or bosses may not be reflected by the config files yet. - turrets blueprints are not used yet. Files modified - plangenerator.lua - shipgenerator.lua - pirategenerator.lua Permissions Feel free to use and expand all files of this mod as it pleases you, as this already modifies Avorion files. I hope you can achieve fun stuff and will share it with the community :) WorkShopShips_v1.0.zip

Hi, I can confirm bolidors bug. If two vessels of the same Alliance show up in the system and use carrier commands the server crashes. They dont have to be controlled by different players. Nor do they need to be controlled by a player at all. It may sometimes take some time to crash. Though I'm not familiar with the patch and game feature situation in patch 17.1 I assume alliances are already in the game. A quick look at the CarrierCommander.lua showed that in the sector callbacks for fighter events a check for the (i guess) mothership enitity checks whether the faction of the ship entity and the fighter are the same. line 163: if Entity(entityId).factionIndex == Entity().factionIndex then That maybe ok if the faction for every mothership that uses carrier commands is different, but otherwise every carrier of the same faction holds messed up references to fighters in their squads. But I'm no LUA pro and I still wonder what part of the script is global and what local. Every Ship a player enters he can access the carrier commands, which lets it look like a local thing, but those callbacks for fighter spawning will probably only work in a global context. Yet in these functions there is a call for Entity() and I guess that is the current Ship in which the script runs. I m confused and wonder why the thing works in the first place :D