Ambiguities/confusion on TutorialAssetSystem Add-a-dice page

[chum]

What you were trying to do

Follow the tutorial.

What actually happened

I got stuck in the add-a-dice section.

How to reproduce

• Read the tutorial as if you completely have never seen anything about Terasology before... ;)

Ok, seriously...

• Tutorial link: https://github.com/Terasology/TutorialAssetSystem/wiki/Add-A-Dice The 2nd part of step 4 says "The RotateBlockOnActivateComponent does not exist yet. We can define it like this:" then has a code block but, unlike the other code-blocks on this tutorial, we are not told where the file containing that code belongs in the hierarchy.

Things are further confusing because my Terasology directory has both... modules/TutorialAssetSystem/{assets, src}/ and tutorial/assetsystem/systems/ directories. I'll guess it goes in one of these and see if things work but, if they don't, I won't know if it's because I goofed the file or put it in the wrong place.

SUGGESTED FIX: add the correct location of the RotateBlockOnActivateComponent [.java?] file to the web page.

Log details and game version

N/A

Computer details

N/A (but it's an iMac running High Sierra with all SWU updates, if you're tracking demographics.)

[devibri]

This confused me at first too. What I ended up doing was looking at the documentation for the module, seeing where the file was placed in there, and then realizing that the top line of the suggested code actually tells you the path that it belongs in. So for instance in the code on RotateBlockOnActivateComponent, the top line reads: package org.terasology.tutorial.assetsystem.components;

So you can create a new set of directories at YOUR_PATH\Terasology\engine\src\main\java\org\terasology to match the ones provided in the package part of the demo code. So for instance the RotateBlockOnActivateComponent.java file will go at YOUR_PATH\Terasology\engine\src\main\java\org\terasology\tutorial\assetsystem\components.

Agree that this can / should be made clearer in the tutorial / documentation though.

EDIT: After seeing more module-s and how they're laid out, I think it's actually appropriate to put these files in a src folder within the module itself, without messing around with the main engine files