Incoming client packet has caused exception starbound ошибка
Обновлено: 04.07.2024
Starbound
19 июл. 2017 в 17:29 helloI have no mods and i play single player
Happen since the last update
"incoming client packet has caused an exception" and it get me on the menu
any help
19 июл. 2017 в 18:24 I reinstalled and now it work but i've lost my 3 characters. 22 июл. 2017 в 21:24 I had this happen today. I ended up removing all Mech related inventory (manufactured parts and blue prints) from my character's inventory and haven't had issue since. 22 июл. 2017 в 21:27
The game will randomly corrupt items which then cause this problem.
Only fix is to track down whatever item it decided to corrupt and trash it.
Gotta love broken updates!
22 июл. 2017 в 21:51 Oh no way I'm going thru all these items to figure out which one broke my game. I was organizing all my million axes and hammers! 25 июл. 2017 в 17:51 For mine, it seems to happen whenever I pick up the corrupted file. But to fix it, I didn't even have to dig through the files, though, I had to survive 2 crashes. I had to pick up the corrupted item [Causing a crash] and when I came back in, I was holding it on the cursor. So then I just dragged it into the bin, which caused another crash, but it removed the corrupted item from my inventory. 26 июл. 2017 в 4:47 I have the same issue. I have just started playing the game and I'm now at the point where I have to collect shards to repair my ship in the mining facility, but every time I get down there the game just crashes ( I have always about 1 - 5 minutes until it crashes). Currently no mods installed. It´s really frustrating. How do I know which item is causing these exceptions? And does anybody know if this will continue throughout the game? Because that would be kind of a dealbreaker :( 26 июл. 2017 в 8:58 Try with another character, if it still crash you should reinstall like me27 июл. 2017 в 1:11 I found the item causing all this, it was a sword. As mentioned above I couldn´t interact with the item without causing a crash, but I was able to delete it, which was also causing a crash, but whatever. Now everything seems to be working again, I'm just hoping that this doesn´t occur more often. 27 июл. 2017 в 21:24
I had this problem as well (single player no mods). I had an item that would cause me to crash whenever I opened my inventory, I couldn't even trash it.
I fixed the problem by killing myself which seemed to drop and disappear the corrupted item.
Starbound
22 июл. 2017 в 13:30 No mods and singleplayer. I have only played for six hours and all the sudden this keeps popping up and now I can't play 22 июл. 2017 в 14:38I was just about to report this. I received this message several times yesterday before the update, and then it has continued after the update. I have played hundreds of hours and never had anything like this happen before, or certainly without this kind of frequency. Within 36 hours I have received this message at least 8 times, and had one total crash of the game.
I have restarted Steam, my computer, and validated the Starbound files. The only things I have not done so far are uninstalled and reinstalled Starbound, or tried running the game without the Steam client.
I am running the game on an iMac (retina, late 2015, 3.3 GHz, 50 GB, AMD Radeon, OSX v10.11.6. There is one security update I need to install for the OS, but otherwise the OS is up to date.
The frequency of this problem is making the game fairly unplayable. And I finally got back into playing (with a fresh start) having experienced the duplication bug which was fixed.
22 июл. 2017 в 15:23 OK, this game is now officially unplayable on my computer. At least I was able to retrieve the chests that I put down just before the last crash. I will check in later to see if there is an update. 22 июл. 2017 в 18:12 Same error try everything game is unplayable. maybe hosting a dedicated server 22 июл. 2017 в 18:33 Same error try everything game is unplayable. maybe hosting a dedicated server I have been exploring if there is a mod problem after the last update. Are you running any mods? 23 июл. 2017 в 7:47Since the last update, the game will decide to corrupt items at random. The only fix is to, with blind luck, find the item responsible and trash it before your game kicks you out.
Had this issue on a singleplayer unmodded character I started a few days ago. Some crappy electric-damage axe was the culprit.
Nice to know at any time, from nowhere, I could have this happen all over again. Thanks, Chucklefish! Your game was more stable in early access.
23 июл. 2017 в 8:12Since the last update, the game will decide to corrupt items at random. The only fix is to, with blind luck, find the item responsible and trash it before your game kicks you out.
Had this issue on a singleplayer unmodded character I started a few days ago. Some crappy electric-damage axe was the culprit.
Nice to know at any time, from nowhere, I could have this happen all over again. Thanks, Chucklefish! Your game was more stable in early access.
23 июл. 2017 в 8:25Since the last update, the game will decide to corrupt items at random. The only fix is to, with blind luck, find the item responsible and trash it before your game kicks you out.
Had this issue on a singleplayer unmodded character I started a few days ago. Some crappy electric-damage axe was the culprit.
Nice to know at any time, from nowhere, I could have this happen all over again. Thanks, Chucklefish! Your game was more stable in early access.
23 июл. 2017 в 8:26Since the last update, the game will decide to corrupt items at random. The only fix is to, with blind luck, find the item responsible and trash it before your game kicks you out.
Had this issue on a singleplayer unmodded character I started a few days ago. Some crappy electric-damage axe was the culprit.
Nice to know at any time, from nowhere, I could have this happen all over again. Thanks, Chucklefish! Your game was more stable in early access.
How did you identify the item?
23 июл. 2017 в 8:29Since the last update, the game will decide to corrupt items at random. The only fix is to, with blind luck, find the item responsible and trash it before your game kicks you out.
Had this issue on a singleplayer unmodded character I started a few days ago. Some crappy electric-damage axe was the culprit.
Nice to know at any time, from nowhere, I could have this happen all over again. Thanks, Chucklefish! Your game was more stable in early access.
How did you identify the item? I looted the item from the Erchius Mine in a chest, I was able to remember which items I most recently picked up and I just started trashing the new items one by one until it worked.
I've heard it happening to items you've owned for a while too though, so blind luck might be your only way.
If you're getting kicked, it does mean it's something in your inventory specifically, and it's always been a weapon for me instead of things like blocks/food/etc.
If you get kicked when opening a chest, it means it's an item inside the chest. Those are all the patterns I've identified thus far.
Item Drop for Survival
Xbawks Character Extender
New comments cannot be posted and votes cannot be cast
After some more experimenting it seems to be tied somehow to a weapon I received in a chest.
Now, if the crashes keep on happening, it may be a mod confliction or something wrong with the modded files themselves.
[07:54:12.048] [Info] UniverseServer: Loading system world (963070254, -504797464, 73704825) from disk storage
[07:54:12.100] [Info] UniverseServer: Spawning player in intro instance protectorate
[07:54:12.149] [Info] Protected dungeonIds for world set to (65524)
[07:54:12.151] [Info] Placing dungeon protectorate
[07:54:12.178] [Info] Placing dungeon at (0, 1000)
[07:54:20.718] [Warn] Failed to place dungeon object: protectoratesmokegen direction: 1 position: (687, 801)
[07:54:20.722] [Warn] Failed to place dungeon object: protectoratesmokegen direction: 1 position: (717, 801)
[07:54:20.733] [Warn] Failed to place dungeon object: protectoratefbannertorn1 direction: 1 position: (725, 802)
[07:54:21.104] [Warn] Failed to place dungeon object: protectoratesmokegen direction: 1 position: (703, 826)
[07:54:21.111] [Warn] Failed to place dungeon object: protectoratesmokegen direction: 1 position: (703, 827)
[07:54:21.127] [Warn] Failed to place dungeon object: protectoratesmokegen direction: 1 position: (700, 828)
[07:54:23.658] [Info] Protected dungeonIds for world set to (0, 65524)
[07:54:28.834] [Info] UniverseServer: Warping player 7 to InstanceWorld:protectorate:7c1b01d119fbdef83d033848cb00d1e0:-
[07:54:31.624] [Error] WorldServerThread exception caught handling incoming packets for client 7: (EofException) Failed to read full buffer in readFull, eof reached.
Читайте также: