Bad Cast timer server return

[moguay]

Can you spend time fixing bugs casting delay, spell casting bar. ie the transmitted information.
cf : http://www.thehiddenforest.org/forum/viewtopic.php?f=2&t=12816&p=75903&hilit=progress+bar#p75903

The crash/disconnection (return to player selection) which I suffer, seems likely to come from there.

Because we are no data cast delay (on some clicky) in Customer EQ, and it creates worries in EQ so be seen in MQ2.
Understand that often happens with the macro, the problem happens also in fight when you manualy uses items (with some condition).

Technically,
When We cast for example Lava Forged Face Guard (Worn Equp), do not have the right server return in the inface EQ "cast progress bar"
> in MQ2 (${Window[CastingWindow].Open} if progress bar) or (${Me.Casting.ID} Spell, if Currently casting)

The problem is strongly accentuated with all Clicky Worn Equip because the items need to be swap.
I am not sure of myself, because we had this problem before the merge.
So I think Vaion to many works on the subject to analyze the cause.

Of course, if you have ideas, I am interested.

[moguay]

With this eqemu version is introduce a casting progression bar data wrong.
It makes mad many plugin and macro based on ${Window[CastingWindow].Open} or some time cast.

I have think a workaround with : the casting text/name return by the server is good, and displayed properly all along cast.
So you can add ${Window[TargetWindow].Child[Casting_SpellName].Text.Length} on all macro casting condition to overcome this problem.

tips:
TargetWindow is the XML UI file name
Casting_SpellName is the flag Pieces name in the XML for configure the Casting Name incoming

[Grey]

Preface: I use to crash toons when I first ported my group macro to suit THF clicks / spells. Yes the lack of viable info on some of the clicks was frustrating but read below.

I just went with global timers. After some work I managed to hack together a plugin for UF to take care of clickies on THF but have not gotten around to updating it for ROF2 and likely wont, went over the source and while it might be better as a plugin the number of lines was more trouble for me to maintain then just a timer.
Also depending on how many you box you might have luck with cast returns either from one of the plugins or .inc files out there.

For ROF2 I opted for a slimmed down casting routine and chose not to filter certain messages so I could trigger events.
I almost never play on the server but when I was on last month to update my macro it all seemed to work fine.

Interesting point on "${Window[CastingWindow].Open}" I'll have to test it, so far I'm not having any issues with it but I agree it might better to check it instead with the other window method.

[moguay]

Interesting reply.

I am convinced that in rof2 the use of clickies in bags could considerably improve the worries that one meets on the worm equip.
Avoid the item switch in the inventory. Do you have a feedback with rof2 ?

Indeed, if we globalize the management of casts, it becomes very complex to develop, nevertheless interesting. This subject is tedious to explain, only for this function I have 120KB macro code, without declarations and initialisation function.
Some good Feat:
- Global queue function (can chain cast in order of big buffing or special boss event for exemple, commanded manually or automatically by the main code, with a priority management)
- Self/Group/Target Buff block check (save the mana)
- Auto Unbuff for special Zone or Class (optimise all buff and song)
- Auto TGB
- Heal HP Break before casting and during casting (save the mana)
- Cast Global Timer and Hard Drive Timer (can keep big timer after a computer reboot, several days, for 24h ability or clicies or after a small desync)
- Cast Data/Status/Type exchange between all bot (optimizes heals/curses/petweapon/sune/rez/coth by exchange all of its informations between all bots, also used with other advanced feat)
- Desync check
- Exchange Item check and restore

That's why I want to manage this part without using other work, there is no equivalent either by plugin or macro code.