Dear Author,

Here is some more information for the 1.69 version update:

This update displays the following error on the X4 Extension settings:

ws_2268673409 .... Location 'x2shippack' already used by another extension.

That is a big clue.

Please fix I need to get back to my game. Thanks for your great work.

I am also a developer for a large company... I did a little research into the extension directory of X4 and it seams that the Steam update system is not updating correctly. It is placing New MOD files in old directories and not naming the new files incorrectly. I can tell this by looking at the modification dates of the files. The problem is I can not fix it because I do not have control of the update system.

Just an FYI. Hope this helps.

You have two different folders of this mod in your "extensions" folder or you mixed cat/dat files with unpacked files. Update can't break anything, it's just new textures, Remove all related to this mod folders and download it from Nexus or Steam Workshop, use only one of them, not both.

I did not update the MOD. The mod was updated by steam automatically which did this to my system. That is my point. The Steam Update system performed poorly. I will try again on Nexus, I no longer trust the steam update system. Other people had problems with Steam Updates. This is not the first time they had problems.

(I already wrote this to the comments section on the mod page)

I had the same issue with 1.69 and now again with 1.70.


The way to fix this on the user side is to:
- close game
- make backups
- delete all 3 directories 'ws_2268673409', 'x2shippack' and 'x2shippack_bak' - those should be versions 1.69, 1.68 and 1.67 respectively in your case
They are located in 'extensions' when you click "Browse local files" in Steam.
- restart the game, mod will be re-installed automatically

I don't know how or even if this is fixable on the mod author's side. To me it seems more like an issue with how the integration and update process in the game works.

Edit: Looked at the date of the original post and changed the mod versions to be 1 lower each

I reported this problem to Egosoft, there is nothing I can do about Steam or workshop tool of this game.

JakoD is correct, it is an issue with the STEAM update system. However, I may have an additional clue. I am currently using my LINUX system to run the game. On Windows the directories names are not CASE sensitive. On Linux or MAC the names are Case Sensitive.

I discovered that one of the old directories is LOW CASE the other directory name is all UPPER CASE. Then the system complains because the XML file is referencing one of these. The Steam Update system updates the wrong Directory Name because it is confuse between the UPPER and LOWER case names.

I think that is a major part of the update issue. On a Windows system the UPPER and LOWER cases will not matter much so there should not be an error if you are using windows to update these directories. However, if you are using Linux the error will occur.

Anyway, from now on I will be updating manually instead of using STEAM.

Anrum.gallente, I love the mod. I hope the information above will help you automate the update process. It might be a quick fix.

There is a way to work around the issue a bit. ext4 got support for being case-insensitive like windows a few years back, but that obviously needs to be enabled manually. it also needs to be configured at file system creation time, but that is likely not something you want to do for your existing filesystem. A workaround I found would be to create an image file, create the ext4 with casefold enabled, mount this image into the extensions folder. a quick rundown:

- cd $gamefolder # eg: cd "/games/steamapps/common/X4 Foundations"
- mv extensions extensions.bak
- mkdir extensions
- dd if=dd if=/dev/zero of=extensions.img bs=1024 count=15728640 # this will create a (roughly) 15GB image file for the mods. choose size depending on your needs
- mkfs -t ext4 -O casefold extensions.img
- sudo mount extensions.img extensions
- sudo rm "extensions/lost+found"
- sudo chattr +F extensions
- sudo chown $(whoami):$(id -gn) extensions
- cp -R extensions.bak/* extensions/

don't forget to add an fstab-entry for the image or remember to remount before launching the game after a reboot. it's not a perfect solution by any means, but I think a workable workaround for these kinds of problems

edit: missed two commands

Chudnofsky: That is a good solution; however, the UPDATES should be automatic on all systems.
No one should have to do the above steps on something that should work out of the box.

It is a good idea but not for most people.
thanks.