I've not had this happen to me and I have been using the UF client since January 2nd.
Does this break like that every time?
_________________
Sorvani
Does this break like that every time?
_________________
Sorvani
Fri May 13, 2011 1:04 pm
Senior Project Member
ok i just set up your version of the macro, and i have the same exact issue.
Put some /echo debug in the macro, and i have some null error as soon as i try to
use a parameter within the NearestSpawn
exemple : from my bard i target my cleric and make a
/tt hot me
my mq2 windows shows [MQ2] ChatType<tell>, Sender<MyBardName>, ChatText<hot me>
and nothing happens
just to be sure....My Everquest login screen figures a dwarf holding some kind of weird figurine...That's the underfoot client right ?
Put some /echo debug in the macro, and i have some null error as soon as i try to
use a parameter within the NearestSpawn
exemple : from my bard i target my cleric and make a
/tt hot me
my mq2 windows shows [MQ2] ChatType<tell>, Sender<MyBardName>, ChatText<hot me>
and nothing happens
just to be sure....My Everquest login screen figures a dwarf holding some kind of weird figurine...That's the underfoot client right ?
Fri May 13, 2011 2:18 pm
Try my mini macro just to be sure blum but I think you and I have the same issue.
Fri May 13, 2011 2:40 pm
only workaround i founded right now is to comment FindExactPC and use a /rt instead.
Ugly, but it works until i can figure why the sub doesn't work
Ugly, but it works until i can figure why the sub doesn't work
Fri May 13, 2011 2:44 pm
you're right, it broked too
copy / pasted your macro, send a tell to the toon with the macro loaded, and i have a ' is not online at this time
the /echo worked though
copy / pasted your macro, send a tell to the toon with the macro loaded, and i have a ' is not online at this time
the /echo worked though
Fri May 13, 2011 2:50 pm
${Param#} is 0 based change that to this:
Expected result:
[MQ2] 0 - tell
[MQ2] 1 - name of person who sent tell
[MQ2] 2 - text of tell
_________________
Sorvani
Macro
Expected result:
[MQ2] 0 - tell
[MQ2] 1 - name of person who sent tell
[MQ2] 2 - text of tell
_________________
Sorvani
Fri May 13, 2011 3:58 pm
Senior Project Member
The PEQ UF build is at fault. I loaded it and can duplicate the problem.
Edit: all the UF builds have this problem.
_________________
Sorvani
Edit: all the UF builds have this problem.
_________________
Sorvani
Fri May 13, 2011 4:13 pm
Senior Project Member
Hello
Is there a patch possible on this, since you said the UF release with in fault ?
I have a workaround for most things so far, but i would be simplier with the initial code of the macro
I saw that the last release of your peq UF mq2 has a manifest date from mid may, maybe it has the fix ?
thanks !
Is there a patch possible on this, since you said the UF release with in fault ?
I have a workaround for most things so far, but i would be simplier with the initial code of the macro
I saw that the last release of your peq UF mq2 has a manifest date from mid may, maybe it has the fix ?
thanks !
Mon May 23, 2011 8:00 am
Soon as we can find where it is bugged we can get it fixed. Chat parse code is a pain to read.
_________________
Sorvani
_________________
Sorvani
Mon May 23, 2011 10:03 am
Senior Project Member
This sounds like a problem I remember from a few years back that occured as soon as Sony added the ability to have people's names as links. (Don't remember why though)
The text looked OK, but something with bleh just didn't come out right, so it hosed all macros for a couple days till someone figured it out..
That wasn't me, but this is the line I added to modbot to repair the problem, and you could possibly adapt it to your UF macros. If the compare is left in, it's backwards compatible in that it does nothing with the SOD client. You would have to edit MsgType, and MsgFrom vaiables in this line to whatever your macro uses, and put it towards the top of your event_chat sub.
Not absolutely sure yours is the same problem though, just sounds like it.
The text looked OK, but something with bleh just didn't come out right, so it hosed all macros for a couple days till someone figured it out..
That wasn't me, but this is the line I added to modbot to repair the problem, and you could possibly adapt it to your UF macros. If the compare is left in, it's backwards compatible in that it does nothing with the SOD client. You would have to edit MsgType, and MsgFrom vaiables in this line to whatever your macro uses, and put it towards the top of your event_chat sub.
Macro
Not absolutely sure yours is the same problem though, just sounds like it.
Sun Jun 05, 2011 9:02 pm
