Looking for an old version

[Arsil PS]

Hello.

I have an odd request. I know it is unlikely but I'll try anyway.

Any chance someone has the installer for the 64bit Linux version of Mote 1.7.12.2 ?

As alternative, is there a way to execute the 32bit version on a 64bit system?

(w/o virtual machine).

Why not using the current version? It's a long and boring story.

[Idle Ideas Inc.]

Sorry, we were hoping that someone would have a copy to share with you. As for the team, we don't archive previous versions, to keep in line with only providing support for the latest version we offer.

What's the issue exactly? Off the top of my head, there is nothing in 1.7.+ that we can't have in 1.16.

[Arsil PS]

That version worked relatively well for my purposes but I couldn't run it on my new 64bit system

(oddly enough, it doesn't even work on a guest 32bit Linux virtual machine - I get segmentation fault).

Ofc I tried the latest 64bit Linux version but most macros of my framework don't seem to work there

(for some I get that decimal expected error message, as if that toggle thingy put on the OnCampaignLoad

macro is ignored, but for most I get no error messages on the chat or the logging window, so no idea what's wrong).

In addition to that, I noticed a few issues with it. Off the top of my head: light sources and auras not

being displayed, buttons with missing tooltips (I know it's not a big deal, but still, you shouldn't

have to do a risky-click to know what they do. IIRC there is one such button of the macro editor)

and... well, that's all I can remember, sorry, it's been a while since the last time I tried to use it.

Also, a simple macro that toggles a status on the selected token(s) doesn't work: it adds the status but

it doesn't remove it if the token already has it. The same macro works as intended on the win64 version.

It takes 2 or 3 seconds after I click on such macro before the UI gets responsive again and allowing to click its button again.

[Arsil PS]

Another issue with the macro editor: in the properties sub-window, the button

on the bottom is cut off, even if you resize the window.

[Idle Ideas Inc.]

please share the problematic campaign/file, and we'll guarantee to get it fixed :)

As for the UI issue, we'll look into it. Linux, yes?

[Arsil PS]

Yes, Linux.I have updated to 1.16.10 in the meantime.

Here's the framework and the steps to reproduce some of the issues.

All example use the same token, pog13, it is the round one.

Here's the steps to reproduce some of the issues:

Select the token.

Click on the campaign macro "Reaction" in the group labeled "700 Toggles"

If you click once, it assign a status to the token and print a message on the chat.

If you click again nothing happens (it is supposed to remove the status).

This macro has always worked before and I've noticed that is works fine in the win64 version of Mote.

In one of my previous message I said that there was a significant delay (2 seconds or so) before I could

press the macro button (or interact with any other element of the UI again) but in this last test I haven't noticed it.

EDIT: nope, the delay still happens, but not always.

Same token, the "Beak" macro (who calls the MeleeWeaponAttack macro in the Lib:Attacks token) doesn't produce any output in the chat.

It looks like the library macro isn't called at all.

Same thing for all the spell macros in the token who call macros from Lib:Spellbook

(who also calls a macro from another library token, it's a bit convoluted but it used to work).

Same token (pog13), try the "3 Faerie Fire (C)" macro.

This checks if that power has already been used, display a text in the chat and then calls the

"darkenMacroButton" macro (a user defined one in OnCampaignLoad in Lib:MacroHelper) that

sets the backgroundcolor of the macro button to display a visual cue that the 1/day power has been used.

(the color is restored to its original by the "Long Rest" campaign macro, currently not working...

actually it seems to work but it doesn't display any message in the chat).

It all works except the last part, it is like the external macro is not even called.

Now, let's consider the "5 Darkness (C)" macro. This works similarly to the previous one but instead

of checking a token property to see if the power has already been spent, it checks the background color

of the macro button calling "isDarkenMacroButton" from Lib:MacroHelper). This macro

gets an error displayed in the chat. Note that "isDarkenMacroButton" is a user defined macro too

and it seem that this is a common factor, in this case the macro is used as part of a condition so

that's probably what causes the error displayed in the chat, while if you simply call the macro

as a command nothing happens).

Now, the elegance of my scripting may well be arguable, but macros like this one worked before and I

have hundreds of saved tokens with macros like this so updating them all would be troublesome.

You can verify on any token that light sources and auras aren't displayed.

Actually, light sources are displayed but only if FOG is enabled.That may be intended behaviour thought, I'm not sure.

Auras, on the other hand, are never displayed.

I know somewhere along the way the format for defining light sources has changed, so maybe my definitions are obsolete?

Anyway, auras should work even when FOG is disabled.

---

Feature suggestion: is it possible for the program to remember the last place (directory)

where you saved a token? Every time I re-open the program and try to save a token

(right clicking on it and choosing "Save...") I get the root directory.

Since the program remembers the path+folder of the last loaded campaign, I guess it

could also remember the path+folder where you last saved a token.

Feature suggestion: is it possible that, when using window.input, the focus goes to the

first element of the "form" instead of the OK button? I realize this is a controversial

request and probably won't work well in most cases, but maybe there is a way to

make it optional (as a parameter of the macro command itself)?

[Idle Ideas Inc.]

thanks for the share. we'll get to it as soon as we can and have an update soon :)

[Arsil PS]

I appreciate that.

I noticed something that seems like a bug.

If you use the rocket button on the quick actions toolbar to edit settings and relaunch Mote,

all the the options chosen for the preferences (Edit->Preferences) are reset to the default values.

Steps to reproduce

Mote menu: Edit-Preferences.

Tick the checkbox "Use Tooltips for Inline Rolls" and confirm (OK button)

Now use the rocket button. No need to change any settings. Let Mote relaunch.

Check Edit-Preferences and that checkbox is back to the default value (unticked).

This happens even if you click "cancel" when you get the warning that says something along the lines:

you selected a non empty dir... you can lose data if use cleaner... are you sure?

[Idle Ideas Inc.]

Quick update. Issues and requests on post with attachment seems all fixed now. More info on upcoming changelog.

Issue on the post after that, is not an actual issue. Committing to a relaunch resets everything. A cancel like the one you mentioned pertains only to that specific setting and not to the launch process itself. HTH.

There are several issues we're still tackling, so a release will come soon after we get those addressed.

Thanks :)

[Arsil PS]

The program forgets - after you close it and restart it - that you ticked "Show Light Sources" in the View menu.

Other options like "Show Grid" are remembered, it seems only a problem with "Show Light Sources"

(I haven't checked them all though).

EDIT: "Show Token Names" isn't remembered either.

Minor issue: that menu entry doesn't use a tick sign but instead uses an icon,

the icon doesn't change if the setting is on or off (like the icon for "Show Grid").

[Idle Ideas Inc.]

IIRC, those settings were never backed by a preferences store, even in MT. Added.

[Arsil PS]

Hey, could you please also check this issue: https://groups.google.com/forum/#!msg/idle_ideas/Zpy6eMrxT3M/AjXKIhQKCQAJ;context-place=categories/idle_ideas

It should be an easy and quick fix (argument non passed in the parser of the input command).

[Idle Ideas Inc.]

Sorry, we weren't able to look at this before making the update. We'll tackle it on the next, if need be.

[Arsil PS]

Mote 1.16.11 on Linux64

Macros that change the bg color of the macro button sometimes update the UI and sometimes not

(I have to de-select and re-select the token to see the change take effect).

Commands to set/remove a status in a token are still hit and miss.

Example: if I use the macro "Faerie Fire" (sometimes it doesn't assign the Concentration status)

and then I use the campaign macro "Conc" to remove it, sometimes it removes it but most of the time it does not.

(the fact that it doesn't remove it is not related to the error you get using the "Conc" macro,

that was likely caused by a "Full API conversion" that replaced "ssetlight" with "slight.set" in resetConcentration in Lib:SpellCasting,

an attempt I did to try to automatically fix the macros and forgot about it).

[Idle Ideas Inc.]

Due to the nature of how MT was made, macro functions, do not have a universal update endpoint. This is why fixes we've done so far in Mote, do not apply to everything. These have to be rooted out one by one, as they are found. Making it universal, is too large a task, for us to tackle right now. It's simply something we're leery of doing. Considering all the large scale stuff we've integrated into Mote, that's saying something LOL

[Idle Ideas Inc.]

fixed