I've got the feeling we are hijacking the Miss Blue Thread a little too much, so I continue in here...
TanyaHumble wrote: ↑Sun Jun 18, 2023 11:57 am
and that it would be as independent from engine as possible. Maybe it's a silly idea with the way superior version in the works.
I don't understand that part of your post, sorry, ... so I can only guess (And PLEASE correct me if I'm guessing wrong!), ...
So, as long as you don't use the new commands from Awakening, it doesn't matter if you play/test/modify a script in a installation of the original Tai or Awakening, you can move the script files back and forth, they are simple text-files anyway.
a test-installation
At the moment I just fix the bugs as I encounter them. I've tried going file by file but it gets really hard for me and I loose focus. My process is , do session -> encounter bug -> depending what bug I either paus the program and look at the script or make a mental note of it. And at the end of the session I read though the log and try to understrand how certain events came to be, look through the moduls and scripts that where used , check if any of them needs any cleaning/bug fixing and then I'm done.
Oh, how much I hear you!
I was there, did kinda the same!
At the moment I just fix the bugs as I encounter them.
This is basically how I work on new scripts, ... I encounter the old version of them, I make notes (or simply a screenshot with the script displayed (CTRL+F11)), and the next day I start to rework/rewrite/correct/rephrase/enlarge/shorten them.
The pro on this is, since you have really played that specific script, you have a much better feeling of what you like to have changed, ... that 'feeling' of that script is 'fresh' in your mind, ... if you 'just' read it while not really playing it isn't enough (for me), you get much better ideas and such if it's played and not only read.
I've tried going file by file but it gets really hard for me and I loose focus.
Exactly!
Have it played -> have a feeling for it!
My process is , do session -> encounter bug -> depending what bug I either paus the program and look at the script or make a mental note of it.
I try to not get too distracted WHILE a session is running.
As I said, I make screenshots, those work as a 'mental note' when I look them up the next day, I don't look up scripts while a session is running.
Oh, ... btw.:
If you hunting down just typos in a script, a simple / small change, you can do this in Awakening 'On-The-Fly', you must have pause activated! (!!!) and then hit CTRL+F11, click on the line you want to change, change it, hit return (!!!) , ... and when you close the program (after the session is done) a window pops up and let you save/reedit such changes you did 'On-The-Fly', ... for small changes like typos and such, this feature can safe you a lot of time!
I'm slowly learning and it will take some time. The heat will 100% slow down my work as it slowly erodes my sleep , kills my mood and destroys me as a human being. So expect to hear less from me over the summer.
Work in the pace you are most comfortable with, make pauses, make sure you don't get a Tai-'burn-out', enjoy the summer, ... I don't 'expect' anything, ... if it ever starts to feel like 'work' then just stop it, ... the best results are done by people who really enjoy what they are doing!
( I do the same, I don't make any pressure on myself, ... I work on it when I have the time for it and when I'm in the mood for it! )
TanyaHumble wrote: ↑Mon Jun 19, 2023 11:38 am
I was running MB on the open beta version and I remember it having some problem with certain variable lines. Later switched to Fury due to another bug and the variable problem seems solved so my guess is that is somehow engine related?
A while ago I did some testing about this, this is from the Awakening Release Notes:
@SetVarString[]
-> I.e.:
@NullResponse @SetVar[Strokes]=[#Random(10,30)]
@NullResponse @SetVar[Speed]=[#Random(60,100)]
@NullResponse @SetVar[Timer]=[Strokes]
The problem is this line:
@NullResponse @SetVar[Timer]=[Strokes]
Correct would be:
@NullResponse @SetVar[Timer]=[#Var[Strokes]]
This line is from the original Tai command guide:
"You can also set string Variables this way, such as @SetVar[MyString]=[lasagna]"
Now different versions of Tai give different results, ... when we take the example from the guide '@SetVar[MyString]=[lasagna]'
In the before-Fury-original-Tai-versions the value of the variable is: '0' (if the variable 'lasagna' doesn't exist)... so it didn't worked as it was explained in the guide, but that way it's used by some personalities.
Also it's impossible to assign a string to a variable with @SetVar[], it ONLY reads it's value if it's exist.
But in Fury, the value of the variable is: 'lasagna' ---> like described in the guide.
That means, using different versions of Tai leads to different results, ... which could lead to incompatibility.
I've thought a while about it and implemented this compromise to be as much compatible as possible to existing scripts/personalities AND to be able to assign a string to a variable:
Let's say the variable 'Strokes' exists, THEN @SetVar will read it's value, if the variable does not exists, the value would be the given string.
The downside of this compromise is that if you would want to assign at another place of the personality the word 'Strokes' to any other variable, it would not be possible since the variable 'Strokes' exists and the value of it would be taken instead the word 'Strokes'. (This is only for @SetVar, @InputVar would work).
To bypass this problem I've added the command @SetVarString[], so even if the variable 'Strokes' exists, with @SetVarString[Whatever]=[Strokes] would work.
Best greetings,
Markus