"Hiccups" like mentioned in the official roadmap: And it just happens that the client modifying mod cause unforseeable and unexpected "hiccups". Those often sound like "when the two of us play together we never have this kind of issue - it is only with you" - which describes an example of a scenario where two players use the same client modifying mod, thinking it would not affect anything on your side and therefore not noticing any issue when playing together since both having the same mod. Even if it is very unlikely and probably only in extremely rare cases. That can be hard as you will have to take your fellow players' words as they are, unable to check yourself if they forgot about their modded sonar GUI or not wanting to share that they are using alternative sailor skins e.g.Įven if you are not using any mods, your fellow sailors using some can cause issues to everyone. you need to be certain that each player, host and clients, are using the same version without any remaining mods. To be certain that an issue is not caused by mods e.g. While in general "all you need to do is the same as mentioned above" people might wonder why it can be a little harder troubleshooting issues which appear in multiplayer sessions. This is why I am recommending the method. Only then you can be sure that no issues created by "leftover" information/files persist. Unsubscribing and deleting the mods properly means to be on the safe side. And all of sudden instead of your favourite chicken dish you are getting fish. Everything works fine at first with your order being accepted as usual. 029 in your favourite restaurant like you did all the years before, not noticing the menu and its numbering has changed. It might "apparently" work at first like normal, but might also cause unforeseeable issues. Like when the game all of sudden uses information from table B which is new in the latest version, but the mods still use a legacy item from table A, despite table A is either deleted or used for something else. Imagine it like a switch being used too quick and it breaks/remembers the current status wrong.īut in most cases it is like mentioned above, with mods getting outdated. In extremely rare cases it can happen that turning a mod on/off can be interrupted by a system's "hiccup". Therefore it makes sense for troubleshooting to reduce the amount of possible reasons which may cause issues. Whether due bad patching or other reasons. In addition to that, having many mods also means having many chances to have corrupted files. Some even need to override vanilla game files entirely. But there are plenty of mods out there which need deeper changes within the game to work properly. And it would indeed suffice just to have them all deactivated. Now when you start Barotrauma again, you can be sure that the game is as vanilla again as it can be, before you installed any mod.Ī good made mod will behave as if it does not exist for the game when it is deactivated. Make sure to backup your own workshop items you want to keep and have not published yet.ĭ) Verify your game's files integrity as described above. Only when both mentioned folders are empty, you can be sure that there are no leftovers from the mods which reactivate by themselves for just being in there. You can access those folders by right clicking on the game from your Steam Library, and then select Manage -> Browse local files. To be thoroughly on the safe side, keeping no leftovers from mods I recommend the following steps:Ī) Deactivate all mods in Main Menu -> Settingsī) Unsubscribe from all mods - you may favourite them so you can easily subscribe to them again after the troubleshooting.Ĭ) Clean up your Barotrauma/Mods and Barotrauma/Workshop folders. To be certain that you are not affected, please remove all Steam Workshop items (aka mods) from the game and check if the problem persists. Unless a Steam Workshop item gets updated simultanously with the game every time, there is a chance of "growing incompatibility over time" which might or might not cause issues. Especially when you consider that each new version of Barotrauma might add or change or remove something in the base game's code which can be essential for a Steam Workshop item to work with the game together. Remove all modsWithout doubts: Barotrauma lives and thrives with its community - and the game is currently best enjoyed with community-made Steam Workshop Items, which add a lot of content while the developers continue working on improving the base game.īut those additions via Steam Workshop can also cause manifold issues.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |