thefloydman / ltta Goto Github PK

Crash Log

Crashes when loading a world.

the example given on page 24 of the guidebook, red color blue color, will result in a color that is exactly half red, and half blue. (128, zero, 128). Colors are always pairwise averaged.

I believe (but have not tested, this is memory) that the order is left to right -- when a color is seen, the existing color value is averaged with the new color symbol, and then that result is saved to either be averaged again in the future or used.

Fisrt of all, gradle refused to use HTTP repo, so I had to replace

maven { url = "http://files.minecraftforge.net/maven" }

with

maven { url = "https://files.minecraftforge.net/maven" }

This allowed build to progress further, but then it stopped with error

FAILURE: Build failed with an exception.

* Where:
Build file '/home/v/compile/LTTA/build.gradle' line: 24

* What went wrong:
A problem occurred evaluating root project 'LTTA'.
> Failed to apply plugin 'net.minecraftforge.gradle.forge'.
   > Configuration with name 'compile' not found.

I'm not familiar with Gradle build system, so I can't fix this one myself.

I imagine this has something to do with this mod, as it never happened before, and there was this recent fix about the library chest being full of Narayani for Dummies.

Forge version: 14.23.4.2765

If I can provide any more relevant details, please let me know.

Black ink has a very low level of instability, but it does have some.

On page 12 in the book, it says "Apple the backboard" instead of "Apply the backboard".

This is the first page of the LTTA book for me:

For some reason, the book opts to show the recipe above with the potion, instead of the more accessible one shown here in JEI:

Not sure what info to give you to help resolve this?

After my experiences with crystal portals, what about some kind of warning on the crystal portal chapter saying that they can malfunction on survival?

gigaherz/Guidebook#48

Opened an issue based on the crashlog I got: gigaherz indicates the error may be on LTTA's side though. Let me know if you need more info, relevant logs repasted here:

Crash log

More helpful segment from debug.log showing the crash happens right after LTTA is referenced