CC: Tweaked

CC: Tweaked

42M Downloads

Non [a-z0-9_.-] character in namespace of location data.lua.treasure

EP1CSAUC3 opened this issue ยท 1 comments

commented

Minecraft version: 1.14.4
Forge version: 28.1.71
CC: Tweaked version: 1.89.0-1.89.1
Mods:

  • CraftTweaker 5.0.1.162
  • CC: Tweaked
  • JEI 6.0.0.27

After attempting to run it 2 possible crashes can occur:

1) Non [a-z0-9.-] character in namespace of location data.lua.treasure_
Which is caused by the capital letters of directories/files inside data.lua.treasure
Replication: running the treasure disk program 'alongtimeago'
Solution: copy program contents from mod files to a program within your word/computercraft

2) Rendering Block Entity/Tesselating Block model
Caused by adding another monitor or removing one
Replication: running the treasure disk program on more than 1 monitor then break one of the monitors beside the computer
Solution: World edit computer + all peripherals out of the game or break the computer

If neither happen another error might occur while running alongtimeago in either disk or local programs:
bios.lua:503 bad argument #1 to 'load' (expected function or string, got nil)

I was able to replicate this with source code and fix the namespace problem but not "bios.lua:503 bad argument #1". I have attached images and a log below. This is my first bug report, hopefully it helps and sorry if I have made any mistakes

Error while loading it from disk/moving it in source code to src\main\resources\data\computercraft\lua\rom\programs\fun
image

Working after copying contents of alongtimeago to "test" program on pc. "monitor left test"
image

Log:
crash-2020-06-22_01.28.16-client.txt

commented

1) Non [a-z0-9.-] character in namespace of location data.lua.treasure._

Treasure disks have been deprecated for a long time now (since 1.79) so I'm afraid this is probably not going to be fixed. In 1.15 they were torn out entirely, and replaced with a datapack which does fix this issue.

2) Rendering Block Entity/Tesselating Block model
Caused by adding another monitor or removing one

This has been fixed in 1.89.1 (see #476) - from the crashlog it appears you were running 1.89.0 at the time. I see you're now running 1.89.1, so hopefully this shouldn't happen again - if it does, please say!