Help With Crash/Bug

[Dubbs Malone]

So I was playing a few minutes ago and I was in an enormous castle a la Better Ruins. I was in a room on an upper floor and I was destroying a bookshelf up against a wall, searching for hidden passages. The bookshelf block broke and either when I picked up the block or when I went to re place the block back in it's spot my game crashed. Attached is the error message I got. I tried to run my save again and it crashed without loading in. I tried to run it in repair mode and it crashed again. 

Does anyone have any insight as to what the issue is? I run a few other mods but nothing that was likely interfering at the time. Carry On, Easy Elk, Metal Recovery, Step Up, Villages, The Dung3on...

 

[Dubbs Malone]

I've tried again without mods loaded and it still crashes on the attempt

Please, anyone. I can't believe my luck with finding such a huge, glorious castle! Check it out!

[Dilan Rona]

you need to report the bug on the better ruins mod page if the crash is from that mod

[Dubbs Malone]

I did. 

[Thorfinn]

Looks like you probably picked up a metal rod of some sort. That's a base game problem. Been reported. Ashantin rolled back to 1.20.4 and then everything was fine. I edited the rod and replaced its graphics with a pick head.

Rolling back is probably vastly easier.

[Dubbs Malone]

2 hours ago, Thorfinn said:

Looks like you probably picked up a metal rod of some sort. That's a base game problem. Been reported. Ashantin rolled back to 1.20.4 and then everything was fine. I edited the rod and replaced its graphics with a pick head.

Rolling back is probably vastly easier.

Thanks very much. I’ll try that. So is it possible to pick up a metal rod by destroying a bookcase?

Also, how do I do that?

Edited March 14, 2025 by Dubbs Malone

[Thorfinn]

I don't know that it was necessarily a metal rod. It could really be any block that uses the same rendering scheme.

That's what the RenderHeldItem( error is telling you. That's probably why 1.20.5 is a release candidate -- there must have been a lot of background engine code rewritten, and it broke some renders, same as it broke shadows in the presence of a helve hammer.

Rolling back is easy. I'd make a backup of all your saves, then do an uninstall  of 1.20.5rc-3. Then do a full install of 1.20.4. When you get whatever it was that was crashing put somewhere safe, where it will never again end up in your hand, you can go back to 1.20.5. Maybe the stable will be out by then, but I doubt it -- I suspect there's going to be a few more RCs patching whatever other crashes are showing up. Not that I know of any others, just sayin'.

[NiclAss]

@Thorfinn

What did you do to edit the item?

maybe I can make a mod with those changes you did tyvm

[Thorfinn]

Since I knew what it was, I just took the pick head json (I think) and copied over whatever I thought had anything to do with stuff in hand into rod json. I know I copied extra just to be on the safe side.

The lines I replaced from behaviors:

	"shape": { "base": "item/rod" },
	"textures": {
		"metal": { "base": "block/metal/ingot/{metal}" },

From attributes:

		onTongTransform: {
			translation: { x: -0.9, y: -1, z: -1.019 },
			scale: 0.8
		}

and then clear down at the bottom:

	guiTransform: {
		translation: { x: 0, y: 0, z: 0 },
		rotation: { x: -48, y: 134, z: 171 },
		origin: { x: 0.53, y: 0.2, z: 0.4 },
		scale: 2.8
	},
	fpHandTransform: {
		translation: { x: 0.28, y: 0.2, z: 0 },
		rotation: { x: 86, y: 180, z: -88 },
		origin: { x: 0.5, y: 0, z: 0.5 },
		scale: 2.15
	},
	groundTransform: {
		translation: { x: 0, y: 0, z: 0 },
		rotation: { x: 0, y: 0, z: 0 },
		origin: { x: 0.5, y: -0, z: 0.5 },
		scale: 4
	},
	tpHandTransform: {
		translation: { x: -0.9, y: -0.05, z: -0.78 },
		rotation: { x: 85, y: 0, z: 2 },
		origin: { x: 0.5, y: 0, z: 0.5 },
		scale: 0.68
	}

Just a brute force script kiddie approach. Someone familiar with how those functions work can probably just fix it right. Assuming the engine code is working as intended.

[EDIT]

Once it was out of my hand, I rolled it back, because it only applies to in-hand. I could craft with it just fine.

Edited March 14, 2025 by Thorfinn

[Dubbs Malone]

So I did as recommended and rolled back to 1.20.4

Crashed again upon loading the save but the error message is a bit different.

Any thoughts?


EDIT ! ! ! --- So, on a last ditch kinda shot I deleted the other, remaining files in the save folder. The files other than the VCDBS regular (I'm relatively outta my depth here) save file. And when I attempted to load the save it FRIGGIN WORKED!!! 

I really don't understand this stuff well enough at all to have any idea but some step(s) of the process of rolling back worked. I have no clue which part exactly, but I'm back in my world, Pangeana, and I get to keep discovering these absolutely incredible structures and I'm just so grateful to you, Thorfinn. Without you I'd have been screwed. Thank you SO MUCH!.

Edited March 15, 2025 by Dubbs Malone
SOMETHING HAPPENED!!!

[Thorfinn]

Weird. I would have thought if you had disabled Better Ruins, any custom blocks would have been replaced by ? blocks. Which I would not think should throw an atlas error. But we are talking graphics now. I am so far out my my lane. When it comes to graphics, being a script kiddie is about all I can do.

Hopefully @NiclAss has an answer, but the only reason I was able to make it work was I knew exactly what it was trying to render. He's going to have to make his best guess from what you remember and can describe.

I hope you make occasional backups of your world at significant mileposts. You will now.  

Edited March 15, 2025 by Thorfinn

[Dubbs Malone]

1 minute ago, Thorfinn said:

Weird. I would have thought if you had disabled Better Ruins, any custom blocks would have been replaced by ? blocks. Which I would not think should throw an atlas error. But we are talking graphics now. I am so far out my my lane. Hopefully @NiclAss has an answer, but the only reason I was able to make it work was I knew exactly what it was trying to render. He's going to have to make his best guess from what you remember and can describe.

I hope you make occasional backups of your world at significant mileposts. You will now.  

 Wait, did you see my edit???

I mean I am so incredibly grateful to you, Thorfinn. I really cannot overstate it. It may seem trivial but because of the experiences I've had on this playthrough it just means so much to me. Thank you for taking the time out of your day to address my problem. You're my hero.

Edited March 15, 2025 by Dubbs Malone

[Thorfinn]

No worries. Hope I didn't say anything that left a bad impression. Not intended in the slightest.

I just noticed from your error log that you were running no mods and that you now had an atlas error. That's not on you -- I have no idea why the base game would not have enough atlas space to render all the graphics in the vanilla game. With luck, someone will stop by who understands that system.

[Dubbs Malone]

Nah I didn’t take offense to anything. I just didn’t know if you saw my post about how the rollback didn’t work or if you saw my edit where I updated that it, in fact, had. 
 

Strangely, though, I’m pretty sure I was running mods when that error was thrown. But this is all relatively over my head so take that for what it’s worth. Regardless, thanks again. So much.

 

 

[Thorfinn]

Oh, no I had not seen the edit. I just reloaded the thread and noticed there was an edit.

Glad you got it working. Be sure to make a backup. That looks like a fun place to explore.

[Maelstrom]

Welp.  I accidently scrolled over a hot copper rod and crashed my game.  Rolled back to 1.20.0 rc1, loaded game, removed problem items (by crafting them into lightning rods), re-installed 1.20..5 rc3 and game loaded just fine.

[Dubbs Malone]

Yeah, I will be creating plenty of backups. The reason I was so emphatic is because I play permadeath and I've been doing arctic starts where I spawn around latitude 75 or higher. In my current playthrough I was on the verge of starvation while also freezing to death on my first day but luckily spotted some ruins off in the distance. Ultimately I found some good stuff in a dungeon there which put me in a position to build a raft with a chest and begin heading south. From there I've been making some great leaps and bounds by way of some very lucky finds and I had progressed so much to even having a sailboat that it would have been such a sin for a run like that, where I went from almost perishing in the frozen wastes to the heights I've reached.

Good times, man.

[flackstacks]

this happened to me too and the crashing has never stopped. I've put in hours since then. The bookcase started it. 

I cant fix it and my heart is breaking. 

Edited June 6, 2025 by eerino

[NiclAss]

@eerino

I need a loc of the bookshelf? Or what bookshelf was it? Can you figure that out for me? Otherwise I can not replicate it to find a reasonable solution

[NiclAss]

I plan on making a mod that will disable that item which might be one way of rescuing people until vanilla fixes this bookshelf.

[flackstacks]

@NiclAss sorry I didn't see this until now! I didn't expect anything from my comment. Location? Shit I really can't recall. I'll look back through my screenshots. I might have taken one when it happened. 

[flackstacks]

@NiclAss I couldn't find the location but I believe I found the shelf. 

[OatmealSwag]

Little late to this but I had the same problem happen to me. I made a back up save just incase then went into repair mode, and it loaded me in.  I didn't save when leaving repair mode (I don't know if it'll make a difference), but when you spawn in under spectator mode take note of where you spawn.  When I loaded back in under regular survival I got through, but it dropped me from a slight height to were I took a little damage.  Where it spawned me wasn't exactly where I crashed and I don't know if it is based on where you left/spawned, in spectator mode. So try to make sure that you are somewhere near the ground when leaving spectator mode, if you die, you can load up the back up and try again.