Gabeux

Hello there. Is all station's production a static value, or is there any way to produce things more efficiently? i.e. Does crew, energy generation, or anything impacts a station (e.g. a Mine) production? Thanks!

I did change that script (since I lost my save/progress), killed the AI 3 times and it wouldn't drop the reward. Not sure what happened.

I've posted this on Steam, but I'm gonna move it here. It's relevant only as long as the crashes occur - hopefully it will all be fixed soon. :D If there's a better way to do/explain things, do let me know. I'm not sure on the effects of deleting a sector or a faction, but I did manage to play for hours on that save with no issues. Thanks! I have survived a hundred server crashes and an instant crash issue due to my sector being bugged - it would CTD immediately after loading. Here's two tips (mostly for singleplayer). Finding your ship Go to your save game folder (%/Appdata/Roaming/Avorion/Galaxies/[Your save game]). and choose your method below. Method 1: Check the logfiles for coordinates - Open the logfile from when the crash occured / when you last had your ship. - Scroll to the end of the file. - Look for lines that refer to "saving sector". It will show coordinates. Take note. - Sometimes, the coordinate is your previous system, sometimes it's the system you were trying to jump to (calculating route) and sometimes it's the right system. Such info is useful for different types of crashes. Use your judgement to prevent unnecessary trips and jumps. Method 2: Search the Sector files for your ship - Go to the sectors folder. - Search for text in files: faction="1" - The newest file that has this text is where your ship is Files that have the searched text are the position of your ship(s) in the universe. The filename is the sector coordinates. Fixing instant sector crashes BEFORE YOU DO THIS: - Close the game and server. - BACKUP YOUR SAVE!!! And do the changes on a copy. - I did not read the game code, so I don't know the full effects of these changes. It's rather extreme. Go to your save game folder (%/Appdata/Roaming/Avorion/Galaxies/[Your save game]). And choose the method that suits your issue: If you (or someone) are crashing on load / stuck on a corrupt sector: - If you are instantly CTDing and don't know what sector you are, use the previous tip to find your ship/location. - Go to the /<galaxy_name>/sectors folder - Open the sector xml file (from the sector that causes CTD). The filename ends with a "v". Example: 100_100v. - Check below the "shipNumbers" tag. There will be a few items, ending with a faction="<number>" in them. - Go to the /<galaxy_name>/factions folder. - Delete the faction .dat files that are present on the <sector>v file ONE BY ONE to prevent unnecessary butchering. That means: Delete a faction, test the save. You might want to open the faction file and look for the faction name (ctrl+f "name") before deleting its file, to assure you're not deleting something important..Or at least to know who you are deleting. (Singleplayer) Faction_1 is you and there's no file for that. If you crash when jumping to a sector, and no one / nothing important is present on that sector: - Go to the /<galaxy_name>/sectors folder. - Open the sector xml file (from the sector that causes CTD). The filename ends with a "v". Example: 100_100v. - Verify that there are no player ships in that sector (under the "shipNames" tag, verify that there are no ships with faction="1"). If there are, then you'll be deleting your own ship(s). - Delete/move both sector files (i.e.: 100_100 and 100_100v). This will make the game regen the sector the next time you jump in. - If issue persists, you can keep deleting the sector until it fixes. Or you can delete the factions present in that sector. Check the above method (Crashing on load) to learn how to do that. Final notes NOTE: I don't know how the game handles player faction IDs in multiplayer servers. Also, you'd need access to the galaxy files anyway. NOTE: I haven't tested the sector fix extensively - but I did recover 2 hours of playtime by doing it, and I played for over two hours with no issues. I also had to delete a sector that would crash my game when I jumped in - no issues. I have no idea how the game handles ships from deleted factions and if this causes any instability or weirdness. I just fixed my save and moved on - this might not be enough for you. NOTE: You will need to open the files manually with a text editor. I recommend Notepad++. PRO TIP: /Save, /save, /save. Backup your save, ESPECIALLY after doing time consuming quests. CTDs and connection losses are but a few jumps away. Good luck, and may the RNG smile upon you.

Thanks for the tip. I actually gave up and looked on the game's code for info and got it. And since I had killed The AI two times before and lost the artifact (due to save loss or derpiness, not sure), I 'cheated' by rewriting some scripts. After that, I had everything to push to the end. And finished it. ;D I have to ask though, is the heavy reliance on RNG luck a good thing? Finding The AI and the MAD Energy Lab took me way too many hours of jumping around. In both cases, back when I didn't know which ranges to look, I was jumping on a ton of Hidden Mass sectors and would never find it since I was a bit too far or a bit too close of the defined range. My suggestion would either give more hints as to where those things are, or make the probability of an encounter rise over time. Maybe even making the probability of an encounter higher if the player hears from a ship about the subject (The AI or the Energy Lab). Maybe I was just insanely unfortunate that made 50+ jumps not be enough, but oh well.

Are there any more tips/clarifications for finding the MAD Energy Lab? I hate spoiling myself things, but after fighting the AI twice and corrupting my save - which forced me to 'butcher' it a bit in order to restore it - I must have spent more than two hours trying to find it.. and it's the last thing I need. ::) To be sure, do you need to jump into Hidden Mass, or Empty Systems? The two times I bumped into the AI was blindly jumping forward without looking for it.