So I’m going through the Code Quickstart Tutorial…
When I input the sample code (the ‘Hello World!’ essentially) into Tinker, it saves without issue and when I execute ‘tinker’ in the world, I receive no error.
However, I do not receive the output.
I have tried typing it in (I like doing this because it helps craft those neural pathways that help me learn) and I have tried copy/pasting it in both, just in case I was missing something somewhere (though I imagine it would have given me an error had I gotten something wrong). The result is the same both times: I receive just the ‘Done!’
This occurs both for the “Hello, #{enactor.name}!” and the following page with the “Hello, #{enactor.name}! Looks like you’re in the #{enactor.room.name}. …” sequence.
What might cause it to execute, but not actually emit to the client?
I’ve tested it on both BSGU and my local test game and I can’t seem to reproduce the issue you’re seeing.
I know on MSB you mentioned installing Ares in a custom environment - is that this same game? If so, you might want to check the server-side permissions. When you edit tinker on the web portal, it triggers the game to actually change the file on-disk. If the game process doesn’t have the right permissions to edit the file, then your changes aren’t really being saved.
You can see if that’s the problem by examining the actual file on-disk (in aresmush/plugins/tinker/commands/tinker.rb) and seeing if it actually contains your changes.
You can also check the log file to see if there are any errors being recorded that just aren’t being shown for some reason.
I’ve figured it out.
It was another matter of me reading things weirdly.
This may happen often I think (or… less frequently as I get a handle on how you wrote the files vs. how I parse them).
The way the tinker editor is structured vs how the file is written is where I was thrown. I was inputting the tutorial information in the wrong place, but where I was inputting it wasn’t actually generating an error so I couldn’t isolate where I was getting it wrong. It still executed just fine, which is why I thought something was potentially breaking somewhere else (the logs were also just fine and dandy, you see :D).
1 Like
Glad you figured it out! I’ve added an extra example to the first tinkering tutorial to hopefully make it a little more obvious where the changes need to go.
While the code itself has been pretty thoroughly battle-tested (between BSGU, 8th Sea and my own testing), not too many folks have run through the coding tutorials. There are bound to be places like this where it was clear to me when I wrote it, but not clear to people who aren’t as familiar with the code. 
Please feel free to point out those places as you go through the tutorials.
1 Like