11
Vote

unable to read beyond the stream

description

ive seen this error a few times through google but i didnt see any solutions.
moreterra was loading my world fine, it still loads others with no problems. on one specific world it stops on "reading chests" and gives me the error, i didnt add any new chests, i even removed a few. the only sawmill in my world would be a random one in a underground house (i saw sawmill on google a few times as a reason this could be happening). i started using terrafirma to help locate some ores and its the same thing, loads other worlds but not this one.

file attachments

comments

trigirl48 wrote Jan 18, 2012 at 2:24 AM

I've got the same thing happening to me. It worked once earlier today then I went to redraw after wandering around a bit and I got the error. The error window says:

System.IO.EndOfStreamException: Unable to read beyond the end of the stream.
at MoreTerra.Structures.World.ReadAndProcessWorld(String worldPath, BackgroundWorker worker)
at MoreTerra.WorldMapper.ProcessWorld(String worldPath, BackgroundWorker bw)
at MoreTerra.FormWorldView.worker_GenerateMap(Object sender, DoWorkEventArgs e)
Version: 1.10.1

I took at the only sawmill I know of in my game and I don't have any signs placed (unless tombstones count but I do my best to pull those up). I tried making a new world and a new character but I still got the error. I read there was an update today, could that have something to do with it?

Gankinu wrote Jan 18, 2012 at 3:35 AM

I'm getting the same error message. All of my different worlds maps i have tried to make get this message.

bootyhunter wrote Jan 18, 2012 at 4:17 AM

yeah thats the same error. i tried making a new world and got the error again. i suppose its not beyond the realm of possibility that the 1.1.2 update could be responsible. might have to wait for moreterra to update??

cff29546 wrote Jan 18, 2012 at 8:44 AM

In the 1.1.2 version, items in the chest are NOT saved as chest.item[i].name followed by chest.item[i].prefix any more (As this is the way in the 1.1.1). Instead, they are saved as chest.item[i].netID followed by chest.item[i].prefix. And this would probably be the reason that MoreTerra can't read new save files correctly.

bootyhunter wrote Jan 18, 2012 at 9:34 AM

i see, thank you. im guessing we have to wait for a 1.1.2 moreterra update to fix this, but how long i wonder?

laranda wrote Jan 18, 2012 at 11:33 AM

got the same error, as to be seen in the screenshot

rackhart wrote Jan 18, 2012 at 12:44 PM

i think this error is caused because of new terraria update.

NamelessOblivion wrote Jan 18, 2012 at 8:39 PM

This is certainly about the Terraria 1.1.2 update not being supported by 1.10.1. This error (or similar) occurs with each new update.

reedhtr wrote Jan 18, 2012 at 10:11 PM

Stream loading code is first failing in ReadChests() in world.cs when it first tries to load the items of a non-empty chest. EndOfStreamException shows up later after code stumbles for a while loading out-of-sync portions of data (like trying to load a merchant NPC as if it's a sign). I second cff29546's assessment of change in stream content happening with chest.item[i].

Ayen_Cat wrote Jan 20, 2012 at 9:43 AM

I had this error, so I did some experimenting. I had 3 other worlds that moreTerra could generate maps for. I found that after PLACING a tombstone in the world (as in died, dug up my grave and placed it as decoration, or a cheap sign) and saving, the world became permanently corrupted from moreTerra's perspective. It doesn't matter if you type text in or not, or if you remove them later, it seems moreTerra will never read that world again. I am using the latest version of moreTerra, btw.

No word if placing and removing a tombstone before saving does this.

ExSalico wrote Jan 21, 2012 at 7:07 PM

I think it has to do with the tombstones i have two worlds that i can make a pic to. and 2 that i cant the 2 that i cant i have removed or placed a Tombstone. Sorta sucks since one of them is my main world :/

lutenentmorriss wrote Jan 21, 2012 at 9:42 PM

i defenetly think it is to do with 1.1.2 update cos i started a new world and as soon as i got on it i opened moreterra loded the world and got that error messege

trigirl48 wrote Jan 22, 2012 at 2:41 AM

I've removed all the tombstones that I've found within my main world but I am also getting the error in fresh brand new worlds where I've not died at all.

Xantu_Volo wrote Jan 23, 2012 at 12:13 AM

I get the same error and so does my my friend raven he has maps made from an older version and those still work. We need updates and that's all there is too it. Its not about tombstones or anything else.

Solsund wrote Jan 24, 2012 at 2:35 AM

Cff had it dead on. They changed it from storing the items in chests by name to by number, because the name would be different depending on the language you chose. This is actually the way Terraria should have done it in the first place and saved themselves a lot of headaches when item names slightly changed but at least it is there now.

The new version is out now. Sorry I did not get to it sooner but I assumed nothing changed that would break the new worlds when I saw the new update notes. I should not have assumed it.

bootyhunter wrote Jan 24, 2012 at 10:09 PM

no worries, i had assumed the same thing based on patch notes and i realize this stuff takes time and that even coders have real life stuff going on. i was stuck using another mapviewer for the time being, it felt like a great inconvenience since moreterra is the first mapviewer i used and my favorite. :) that said, thank you for updating moreterra.

Sign in to add a comment or to set email notifications