All Activity

Can you test 2.5.11 (beta)? Does the problem occur with 2.5.11 as well? If it does, less often or about the same as with 2.5.10?

More clearer background texture, starry sky, and more interesting planets. The ship can make a long time, but the longer playing time is monotonous and the limited repetitive environment is the most dirty person ...

sometimes i like to have a specific amount of fighters on my ships, i would like to see a simple limiter for the number of fighters that the ship will produce per flight.

QoL & Bugfixes Beta Branch Note: These changes are currently available on the beta branch. The beta branch is for testing experimental changes and for finding and fixing errors. This is how you get access to the beta branch (USE AT YOUR OWN RISK): Right-Click on Avorion in your Steam list, Properties -> Betas -> Select branch 'Beta Branch - Newest Changes & Experimental Features'. Gameplay (Into The Rift) Acid Fog environmental effect is less severe now Overall damage is slightly reduced; maximum damage has been halved Affected material progression has been shifted towards the center of the galaxy, so that there is more of the next safe material available in nearby sectors Rift Research Data loot is now marked when using an object detector Scannable radiating asteroids change their color back to normal after being used Added a visual indicator when ships are getting damaged from radiating asteroids Quantum Xsotan now stay closer to the fight Activated wormhole generators are now highlighted and shown in Strategy Mode's sector overview Quality of Life Added preview for new mass and new number of subsystem sockets when scaling ship in Build Mode (in Modify Whole Ship window) UI Strategy Mode: added message beacons, sector renaming beacons and marker buoys to sector overview Added "delete word" functionality to multiline text boxes (Ctrl+Backspace and Ctrl+Delete) Input dialog windows (e.g. ship renaming) can now be confirmed with "Return" Photo Mode now has HUD buttons to exit Photo Mode and to show/hide the Photo Mode window Performance Optimized spawning multiple Xsotan at once The game will still have a short performance impact when spawning new ships, but it should be much better now Optimized cleanup of overlapping blocks when importing a craft/template/turret Scripting API Added new function WaveUtility.createXsotanWaveAsync(namespace, callback, ...) that allows for async generation of predefined groups of Xsotan this function's spawning behavior is exactly like the existing WaveUtility.createXsotanWave() even if you do not want to use the callback parameter, the namespace parameter has to be given in order for the internal callback structure to work Added Sector():dropTorpedo(...) that drops a torpedo as loot at the given position Bugfixes Fixed an issue in Build Mode where undoing ship scaling would result in lost turrets Fixed an issue where marker buoy messages would not be shared between all permitted players Fixed an issue where rift mission cargo would not be removed after ending the mission Fixed an issue where objects in rifts were not scannable by player drones (using the player drone in a rift sector is not recommended, though) Fixed an issue where Build Mode's subsystem socket icons would not update correctly when changing ship size [UBR] Fixed an issue where ship building progress was no longer visible at the shipyard after saving and reload [UBR] Fixed an issue in Free Play settings (when creating a new galaxy) where the unlimited maximum ship size checkbox was incorrectly disabled Fixed an issue where camera would jump when entering Photo Mode if Cruiser Steering Mode was active Fixed an issue where some HUD buttons were visible in Photo Mode [UBR] Fixed Turret Build Mode requiring Titanium building knowledge to build [UBR] Fixed Turret Build Mode showing additional unavailable block types if player is missing some building knowledge [UBR] Fixed several issues in torpedo tutorial [UBR] Fixed rift teleporter being boardable [UBR] Fixed an issue where the tooltip of dropped loot is showing in a wrong position when using a custom UI scale [UBR] Fixed casino not showing up in the encyclopedia's goods glossary (UBR = User Bug Report)

Problem solved! Updating the drivers for my external audio interface (Minifuse 2) fixed the crash. The game now launches and runs perfectly. Thank you for the accurate diagnosis about the audio issue!

On first glance the stack trace looks like an issue with audio. Can you try to reinstall audio drivers? If you are using your mainboards onboard audio, try using the newest audio drivers from the mainboard manufacturer website. You can also try to change the default audio device (for example if you have onboard audio and another audio device for sound over HDMI) before starting Avorion. Please report back what you try and if one of those steps fixes it. If the problem persists, tell us more about your audio device(s).

Subject: Game crashes on startup with EXCEPTION_ACCESS_VIOLATION during script loading Game Version: actual steam OS: Windows 10 GPU: NVIDIA GeForce RTX 4060 GPU Driver: 581.81 CPU: AMD Ryzen 7 5700X RAM: 16GB Problem Description: The game consistently crashes during startup with an EXCEPTION_ACCESS_VIOLATION error. The crash occurs during the script initialization phase, after basic graphics and system initialization are completed successfully. What I've already tried: Installed latest NVIDIA Game Ready drivers (clean installation with DDU) Installed/updated Microsoft Visual C++ Redistributables and .NET Framework Verified game files integrity through Steam multiple times Completely uninstalled and reinstalled the game Tried various launch parameters (-windowed, -safe, -nosound, -disablepreload, -force-opengl) Reset all configuration files (deleted settings.ini) Ran the game in Windows compatibility modes Disabled fullscreen optimizations Performed clean boot to eliminate software conflicts Reinstalled OpenAL manually Error Pattern: The game initializes successfully until the script loading phase, then crashes with: text Thread 1 Error: EXCEPTION_ACCESS_VIOLATION Thread Name [28]: Lua WorkerPool Thread 3 The crash occurs consistently at the same point in the initialization process, regardless of graphics settings or launch parameters. Additional Observations: Graphics subsystem initializes correctly (OpenGL 4.0 context created) Window creation successful OpenAL context creation shows error, but crash happens later during script loading Game doesn't respond to -nosound parameter (still crashes) Standard troubleshooting steps haven't resolved the issue Complete log files attached. Question: Has anyone encountered similar startup crashes in version 2.5.10? Are there any known issues with script initialization or Lua worker threads in the current version? Any guidance would be greatly appreciated. Thank you! clientlog 2025-11-24 19-51-49.txt

I fire it from any range, in tube 1, by pressing G, nuclear type, other types tried too. Adventurer just says dang, and gives me another torpedo. Can't complete. Most annoyingly, it resets you to targeting the adventurer, so if you're not carefully watching, your next torpedo target is him. This has been an issue for years. This tutorial, imo, should be removed or overhauled, since it has been a nuisance for a long time. I just want it off my mission list, personally.

In the Turret and Inventory screens there are options for Rarity, Material, DPS DPS/slot, but there is no option to sort by range. This will be helpful if you are building a short medium or long range attack vessel so you can scale the range of your equipped weapons. For example, If I want a missile boat with some long range shooting capability I want to make sure that I dont have to fly too much closer before I can reach, or if I have a vessel that has high damage close range weapons I will want to look for similar weapons for that style of combat.

i have both code fragments for Operation Exodus but when i enter them it says access denied any thoughts?

Am I right in understanding that you don't always have a high ping in single player in Avorion? How can you tell that you have a high ping in single player? Can you describe this in more detail? It would also be interesting if you could enable the ‘FPS Counter’ and ‘Frame Time Graphs’ options under Settings -> Video and let me know what information they display in situations where there is lag. Furthermore it is always recommended to send us client and serverlogs of related play sessions because they give us valuable information that can help identifying the problem. The server logs are located at %appdata%/Avorion/galaxies/*YourGalaxyName*/… The client logs are located at %appdata%/Avorion/…

Hey, I've played this game back in 2020, but there's always this issue of lag, because the game runs on a server on my pc, idk the details, but it just caused a lot of lag, like i have super high ping on some online game, but it's single player, have you fixed this issue yet?

Long time no play. I'd like to make a suggestion: AVORION 2!!! Now an MMORPG with NPC factions controlling the center of the universe. Its 1000 years in the future and more advanced materials technologies have appeared allowing for unique alloy compositions and smelting! The Alien threat has long been eliminated... or has it? The rifts remained after the reconquering of the core systems of the universe. After being reconnected with the core systems the empires in the center of the universe have flourished with the new introduction of avorion. The Alien menace then invaded from the rifts that were neglected. The core systems held strong but small pockets remain outside the core systems barely holding on. It is up to the players to fight back and reclaim the old empires that once fought against the Aliens over 1000 years ago! The further from the center you get the stronger the alien menace becomes... And they are equipped with unique materials from the rifts in which they incubated. General overview of changes to the sequel: - Optimized (or new) engine for multiplayer and large-scale battles. - Materials alloying (combining 2-3 materials when smelting giving blocks with unique parameters that is inefficient but useful for making stronger ships) - Ultra rare rift materials that can only be found in rifts during raids or from mini-bosses/bosses emerging from the rifts. - Core systems are governed by strong police forces providing a "safe zone" for players to build up to venture outside of the core and do missions. - Player diplomacy with other corporations and NPC corporations - System sovereignty and defense automation - Make it harder to solo build an empire economy wise (leaning more into the MMO aspect) - Corporation ship and turret designs and doctrines (includes modular ship building functionality - Combat overhaul with balancing against PVP and PVE in mind (new turrets, defense mechanics, cloaking, mines, capital class weapons, ect). - Balancing of "brick ships" (may require sacrificing how much of a block can overlap with another) - Overhaul of materials refining, goods production/automation - Warp animation, Fleet formations, Fighter/gunship overhaul, ect from other worthwhile suggestions for a great experience 🙂

Hello everyone, I'm trying to create a subsystem mod that would increase the braking force (inertia damping), but I can't figure out what characteristics the subsystem should change. I also tried to find information to simply change the efficiency of the inertial damper block, but to no avail. I would appreciate any help.

As the patch was performing nicely on beta - here it is now live on default! Additionally to the below patchnotes we also fixed some flagged issues in the Japanese translation 🙂 ITR Gameplay Rifts prevent Ore purification. Previously this meant that you could not mine asteroids in rifts with Purifying Mining Lasers at all. Now they can break up rift stone like R-Mining Lasers, but not as efficiently. Secondary objective objects are no longer dockable to avoid confusion Object Detectors can now detect and highlight the Time Device Added additional dialog to the Time Device to make it clearer that you need to complete all Into The Rift story missions before you can use it Improved description of Xsotan Core Extraction mission objectives ITR QoL Rift extraction is now always visible in HUD (for Ripcord, Wormhole Generator, Wormhole Device) Rift teleport (both into the rift and out of it via Ripcord) can now be canceled Improved the teleporters "Go-To" dialog option: in addition to being moved to the teleporter, the player ship is now oriented towards it If a ship needs to be restored out of a rift sector after a crash, it is no longer silently moved to players reconstruction site If it's a player ship, it's restored at the last repair dock the player has seen (the same sector the player will respawn at) If it's an alliance ship, it's restored at the reconstruction site of one of the alliance members and all alliance members are informed by mail Xsotan Hunter Captain's chat messages now show the ship's name instead of the ship's class (as class is just "Ship" by default) Bugfixes Fixed a crash when removing entities with pending updates from a sector [UBR] Fixed a crash when there were very high amounts of loot in the sector and optimized handling of glow particles [UBR] Fixed a crash that occurred when player ships were destroyed right at the start of a camera animation [UBR] Fixed a crash when entering a new sector related to loot rendering [UBR] Fixed an issue where non-functional cube ships would be generated for NPCs [UBR] Fixed an issue where repair platforms were unable to restore any blocks that were lost since entering the rift sector if the ship was initially over the rift missions weight limit Fixed an issue where partial secondary objective descriptions were displayed for the currently tracked mission Fixed some descriptions in missions not being translated Fixed an issue where the continue button in the main menu was disabled after version updates (Note: Even if the continue button is disabled, previous galaxies are still accessible through "Singleplayer") (UBR = User Bug Report)

While we can not provide official support for containers, one line of this log stands out to me: "Error finding home directory" Make sure the linux user inside the container has a home directory and has an entry in /etc/passwd. I'm curious if this helps, so please report back.

I’m having issues with faction packs in xavorion I am also using the faction pack sub mod, maybe someone could shed some light on this log.

Beta Branch Note: These changes are currently available on the beta branch. The beta branch is for testing experimental changes and for finding and fixing errors. This is how you get access to the beta branch (USE AT YOUR OWN RISK): Right-Click on Avorion in your Steam list, Properties -> Betas -> Select branch 'Beta Branch - Newest Changes & Experimental Features'. ITR Gameplay Rifts prevent Ore purification. Previously this meant that you could not mine asteroids in rifts with Purifying Mining Lasers at all. Now they can break up rift stone like R-Mining Lasers, but not as efficiently. Secondary objective objects are no longer dockable to avoid confusion Object Detectors can now detect and highlight the Time Device Added additional dialog to the Time Device to make it clearer that you need to complete all Into The Rift story missions before you can use it Improved description of Xsotan Core Extraction mission objectives ITR QoL Rift extraction is now always visible in HUD (for Ripcord, Wormhole Generator, Wormhole Device) Rift teleport (both into the rift and out of it via Ripcord) can now be canceled Improved the teleporters "Go-To" dialog option: in addition to being moved to the teleporter, the player ship is now oriented towards it If a ship needs to be restored out of a rift sector after a crash, it is no longer silently moved to players reconstruction site If it's a player ship, it's restored at the last repair dock the player has seen (the same sector the player will respawn at) If it's an alliance ship, it's restored at the reconstruction site of one of the alliance members and all alliance members are informed by mail Xsotan Hunter Captain's chat messages now show the ship's name instead of the ship's class (as class is just "Ship" by default) Bugfixes Fixed a crash when removing entities with pending updates from a sector [UBR] Fixed a crash when there were very high amounts of loot in the sector and optimized handling of glow particles [UBR] Fixed a crash that occurred when player ships were destroyed right at the start of a camera animation [UBR] Fixed a crash when entering a new sector related to loot rendering [UBR] Fixed an issue where non-functional cube ships would be generated for NPCs [UBR] Fixed an issue where repair platforms were unable to restore any blocks that were lost since entering the rift sector if the ship was initially over the rift missions weight limit Fixed an issue where partial secondary objective descriptions were displayed for the currently tracked mission Fixed some descriptions in missions not being translated Fixed an issue where the continue button in the main menu was disabled after version updates (Note: Even if the continue button is disabled, previous galaxies are still accessible through "Singleplayer") (UBR = User Bug Report)

(repost: https://steamcommunity.com/app/445220/discussions/1/594032343582426624/ ) The client freezes when running rifts. I guess this one got reported a lot, but is still not fixed. I was able to play 1 rift till completion, the following 8 not...so can reproduce it really good. Step-by-step instructions on how to reproduce the bug. Start a rift wait for 5-60 minutes, then the client freezes. At least for me. Your system specs: Operating System win 11 CPU AMD Ryzen 9 3900X with 64GB RAM GPU AMD Radeon RX 6900 XT driver 25.8.1 exit log: 2025-08-26 16-34-58| Thread [HangDetector] with id 32 exiting... 2025-08-26 16-34-58| Thread [HangDetector] with id 32 exited 2025-08-26 16-34-58| Exited client main loop. 2025-08-26 16-34-59| Starting thread [Server Shutdown]... 2025-08-26 16-34-59| Started thread [Server Shutdown] with id 48 2025-08-26 16-34-59| Error sending message of type: 58: can't send a when not connected 2025-08-26 16-34-59| Starting thread [UDP Connection Receive]... 2025-08-26 16-34-59| Started thread [UDP Connection Receive] with id 49 2025-08-26 16-34-59| Client UDP: Error receiving from 127.0.0.1, error: An existing connection was forcibly closed by the remote host, received bytes: 0 2025-08-26 16-35-02| Thread [Steam Networking Receive] with id 45 exiting... 2025-08-26 16-35-02| Thread [Steam Networking Receive] with id 45 exited 2025-08-26 16-35-02| Thread [UDP Connection Receive] with id 44 exiting... 2025-08-26 16-35-02| Thread [UDP Connection Receive] with id 44 exited 2025-08-26 16-35-02| UDP closed 2025-08-26 16-35-02| Client UDP: Connection closed 2025-08-26 16-35-02| Thread [UDP Connection Receive] with id 43 exiting... 2025-08-26 16-35-02| Thread [UDP Connection Receive] with id 43 exited 2025-08-26 16-35-02| UDP closed 2025-08-26 16-35-02| Client UDP: Connection closed 2025-08-26 16-35-02| Stopping local server ... 2025-08-26 16-35-02| Client UDP: Error receiving from 127.0.0.1, error: No connection could be made because the target machine actively refused it, received bytes: 0 2025-08-26 16-35-02| Client UDP: Error receiving from 127.0.0.1, error: An existing connection was forcibly closed by the remote host, received bytes: 0 2025-08-26 16-35-03| Server shutdown successful. 2025-08-26 16-35-03| Thread [UDP Connection Receive] with id 49 exiting... 2025-08-26 16-35-03| Thread [UDP Connection Receive] with id 49 exited 2025-08-26 16-35-03| UDP closed 2025-08-26 16-35-03| Client UDP: Connection closed 2025-08-26 16-35-03| Thread [Server Shutdown] with id 48 exiting... 2025-08-26 16-35-03| Thread [Server Shutdown] with id 48 exited 2025-08-26 16-35-03| Thread [Game WorkerPool Thread 0] with id 2 exiting... 2025-08-26 16-35-03| Thread [Game WorkerPool Thread 0] with id 2 exited 2025-08-26 16-35-03| Thread [Game WorkerPool Thread 1] with id 3 exiting... 2025-08-26 16-35-03| Thread [Game WorkerPool Thread 1] with id 3 exited 2025-08-26 16-35-03| Thread [Game WorkerPool Thread 2] with id 4 exiting... 2025-08-26 16-35-03| Thread [Game WorkerPool Thread 2] with id 4 exited 2025-08-26 16-35-03| Thread [Game WorkerPool Thread 3] with id 5 exiting... 2025-08-26 16-35-03| Thread [Game WorkerPool Thread 3] with id 5 exited 2025-08-26 16-35-03| Thread [Game WorkerPool Thread 4] with id 6 exiting... 2025-08-26 16-35-03| Thread [Game WorkerPool Thread 4] with id 6 exited 2025-08-26 16-35-03| Thread [Game WorkerPool Thread 5] with id 7 exiting... 2025-08-26 16-35-03| Thread [Game WorkerPool Thread 5] with id 7 exited 2025-08-26 16-35-03| Thread [Game WorkerPool Thread 6] with id 8 exiting... 2025-08-26 16-35-03| Thread [Game WorkerPool Thread 6] with id 8 exited 2025-08-26 16-35-03| Thread [Game WorkerPool Thread 7] with id 9 exiting... 2025-08-26 16-35-03| Thread [Game WorkerPool Thread 7] with id 9 exited 2025-08-26 16-35-03| Thread [Game WorkerPool Thread 8] with id 10 exiting... 2025-08-26 16-35-03| Thread [Game WorkerPool Thread 8] with id 10 exited 2025-08-26 16-35-03| Thread [Game WorkerPool Thread 9] with id 11 exiting... 2025-08-26 16-35-03| Thread [Game WorkerPool Thread 9] with id 11 exited 2025-08-26 16-35-03| Thread [Game WorkerPool Thread 10] with id 12 exiting... 2025-08-26 16-35-03| Thread [Game WorkerPool Thread 10] with id 12 exited 2025-08-26 16-35-03| Thread [Game WorkerPool Thread 11] with id 13 exiting... 2025-08-26 16-35-03| Thread [Game WorkerPool Thread 11] with id 13 exited 2025-08-26 16-35-03| Thread [Game WorkerPool Thread 12] with id 14 exiting... 2025-08-26 16-35-03| Thread [Game WorkerPool Thread 12] with id 14 exited 2025-08-26 16-35-03| Thread [Game WorkerPool Thread 13] with id 15 exiting... 2025-08-26 16-35-03| Thread [Game WorkerPool Thread 13] with id 15 exited 2025-08-26 16-35-03| Thread [Game WorkerPool Thread 14] with id 16 exiting... 2025-08-26 16-35-03| Thread [Game WorkerPool Thread 14] with id 16 exited 2025-08-26 16-35-03| Thread [Game WorkerPool Thread 15] with id 17 exiting... 2025-08-26 16-35-03| Thread [Game WorkerPool Thread 15] with id 17 exited 2025-08-26 16-35-03| Thread [Game WorkerPool Thread 16] with id 18 exiting... 2025-08-26 16-35-03| Thread [Game WorkerPool Thread 16] with id 18 exited 2025-08-26 16-35-03| Thread [Game WorkerPool Thread 17] with id 19 exiting... 2025-08-26 16-35-03| Thread [Game WorkerPool Thread 17] with id 19 exited 2025-08-26 16-35-03| Thread [Game WorkerPool Thread 18] with id 20 exiting... 2025-08-26 16-35-03| Thread [Game WorkerPool Thread 18] with id 20 exited 2025-08-26 16-35-03| Thread [Game WorkerPool Thread 19] with id 21 exiting... 2025-08-26 16-35-03| Thread [Game WorkerPool Thread 19] with id 21 exited 2025-08-26 16-35-03| Thread [Game WorkerPool Thread 20] with id 22 exiting... 2025-08-26 16-35-03| Thread [Game WorkerPool Thread 20] with id 22 exited 2025-08-26 16-35-03| Thread [Game WorkerPool Thread 21] with id 23 exiting... 2025-08-26 16-35-03| Thread [Game WorkerPool Thread 21] with id 23 exited 2025-08-26 16-35-03| Thread [Game WorkerPool Thread 22] with id 24 exiting... 2025-08-26 16-35-03| Thread [Game WorkerPool Thread 22] with id 24 exited 2025-08-26 16-35-03| Thread [Game WorkerPool Thread 23] with id 25 exiting... 2025-08-26 16-35-03| Thread [Game WorkerPool Thread 23] with id 25 exited 2025-08-26 16-35-03| Thread [Analytics WorkerPool Thread 0] with id 30 exiting... 2025-08-26 16-35-03| Thread [Analytics WorkerPool Thread 0] with id 30 exited 2025-08-26 16-35-03| Thread [Analytics WorkerPool Thread 1] with id 31 exiting... 2025-08-26 16-35-03| Thread [Analytics WorkerPool Thread 1] with id 31 exited 2025-08-26 16-35-03| Thread [AmbientOcclusion WorkerPool Thread 0] with id 41 exiting... 2025-08-26 16-35-03| Thread [AmbientOcclusion WorkerPool Thread 0] with id 41 exited 2025-08-26 16-35-03| Thread [AmbientOcclusion WorkerPool Thread 1] with id 42 exiting... 2025-08-26 16-35-03| Thread [AmbientOcclusion WorkerPool Thread 1] with id 42 exited 2025-08-26 16-35-03| Thread [Lua WorkerPool Thread 0] with id 33 exiting... 2025-08-26 16-35-03| Thread [Lua WorkerPool Thread 0] with id 33 exited 2025-08-26 16-35-03| Thread [Lua WorkerPool Thread 1] with id 34 exiting... 2025-08-26 16-35-03| Thread [Lua WorkerPool Thread 1] with id 34 exited 2025-08-26 16-35-03| Thread [Lua WorkerPool Thread 2] with id 35 exiting... 2025-08-26 16-35-03| Thread [Lua WorkerPool Thread 2] with id 35 exited 2025-08-26 16-35-03| Thread [Lua WorkerPool Thread 3] with id 36 exiting... 2025-08-26 16-35-03| Thread [Lua WorkerPool Thread 3] with id 36 exited 2025-08-26 16-35-03| Thread [UI WorkerPool Thread 0] with id 26 exiting... 2025-08-26 16-35-03| Thread [UI WorkerPool Thread 0] with id 26 exited 2025-08-26 16-35-03| Thread [UI WorkerPool Thread 1] with id 27 exiting... 2025-08-26 16-35-03| Thread [UI WorkerPool Thread 1] with id 27 exited 2025-08-26 16-35-03| Thread [UI WorkerPool Thread 2] with id 28 exiting... 2025-08-26 16-35-03| Thread [UI WorkerPool Thread 2] with id 28 exited 2025-08-26 16-35-03| Thread [UI WorkerPool Thread 3] with id 29 exiting... 2025-08-26 16-35-03| Thread [UI WorkerPool Thread 3] with id 29 exited 2025-08-26 16-35-03| glGetError returned error code twice. Please check that the current thread owns the OpenGL context. 2025-08-26 16-35-03| glGetError returned error code twice. Please check that the current thread owns the OpenGL context. 2025-08-26 16-35-03| glGetError returned error code twice. Please check that the current thread owns the OpenGL context. 2025-08-26 16-35-03| glGetError returned error code twice. Please check that the current thread owns the OpenGL context. 2025-08-26 16-35-03| glGetError returned error code twice. Please check that the current thread owns the OpenGL context. 2025-08-26 16-35-03| glGetError returned error code twice. Please check that the current thread owns the OpenGL context. in full: (last 2 freezes) clientlogs https://pastebin.com/tgGSqwTJ https://pastebin.com/0ybGGMcv serverlogs https://pastebin.com/Nz9HuFPi https://pastebin.com/MrpCy5wV adding one from today: client https://pastebin.com/YdMJRnpL server https://pastebin.com/rT93S9rW

Updated Ukrainian localization: https://drive.google.com/file/d/10Fijk7boqEEpITxylAg5EFrdnKnmuIZw/view?usp=sharing

Оновлений переклад з робочим посиланням: https://drive.google.com/file/d/10Fijk7boqEEpITxylAg5EFrdnKnmuIZw/view?usp=sharing Avorion_UA.zip

Thank you for the update and pointing that out!

As seen in the video below when put into automation mode my miners attack stations and other ships to "mine" the ressource asteroid behind said ship or station Aufzeichnung 2025-08-04 123615.mp4

Since this Post got necrod, I think this is a new crash since I cant replicate it anymore in the current game Version on my end.

It would be important if you could send me the corresponding client log (and server log if possible). The client logs are located at: %appdata%/Avorion/… The server logs are located at %appdata%/Avorion/galaxies/*YourGalaxyName*/…