cure buttons - problem
 

i am trying to change the cure buttons (inside the groupwindow xml)to:

x) jester the respective groupmember
x) send him a tell
x) send a msg to a custom channel

----------------------------------------------------

now:

OnPress="say Jesters Cap" <= char says "jesters cap"

OnPress="say Jester's Cap" <= char does nothig

OnPress="tell Target="Parent.Parent.GroupMember1.MemberInfoPage.Name.Text blah" <= tells gm1 'blah'

OnPress="useabilityonplayer Target=Parent.Parent.GroupMember0.MemberInfoPage.Name.Text Allegretto" <= This Spell or Ability is no longer available

OnPress="useabilityonplayer Target=Parent.Parent.GroupMember0.MemberInfoPage.Name.Text Jester's Cap" <= This Spell or Ability is no longer available

OnPress="useabilityonplayer Target=Parent.Parent.GroupMember0.MemberInfoPage.Name.Text Jester&apos;s Cap" <= This Spell or Ability is no longer available

-------------------

hmmm - can anyone please tell me why it doesn't work, and what i have to put there?

They don't work because that is neither valid XML nor valid eq2 command syntax, you are lucky it didn't just crash the game (in particular your third try). Search function is at the top and there are also two released tools for configuring the macro buttons (you said cure buttons but posted macro button code) automatically.

of course i used the search function but didn't get what i want - please also see: http://www.eq2interface.com/forums/s...ad.php?t=11587

okay so what i want to do is replace the curebuttons in 'eq2ui_mainhud_groupmembers.xml' with a single button that jesters the player, sends him a tell that he has been jestered, and sends a tell to a custom channel (eg: /2) that player X has been jestered =)

btw. what i posted above are just snippets -

doesn't work either.



-------------------------------------------
quickraidbuttons.txt:

i tried the quickraidbuttons also:

doesn't work :>

-----------------------------------

ingame macros also wont work, due to lag:

/target group_member 0
/useability Jester's Cap
/tell %t Jester's incoming
/2 Jester's on %t
/target_previous


while jesters hits the right target, both msgs are send to the previous target instead of the group member :(

The Target= syntax you're using inside of commands is plain weird. I don't know why that would work to begin with. useabilityonplayer is a game command and target is a game command. Yet you're using one inside of another? As far as I understand the command parser, it should be trying to execute a command named Jester's Cap, execute target on the player then execute useabilityonplayer with no arguements. Target=Player is correct syntax for a target command, but not in the context you are using it. Just type the command how you would in-game if you're using one line per command.

To repeat myself: There is a million posts with working code on how to add a tell to the JCap quick macro button on these forums. Alternatively just use my automatic configurator if you have Excel. Also you can't just put the quick macro button code in the cure buttons, they are set up differently and "Parent.Target" does not mean anything to them.

PS: Aditu, what he posted is a bit of a random mix of my cure button code and my macro button code, both of which store the target name to a variable named Target (albeit in a previous step in my code).

Oh, heh. Well, command=args being acceptable syntax for single line commands threw me off that it might have been copied from something else completely.

but if Target=Parent.Parent.GroupMember1.MemberInfoPage.Name.Text was issued twice in a row you would target gm1 :P.

No I agree, I don't understand either how the target= bit could work for him, that's not from me.

ingame macros also wont work, due to lag:

/target group_member 0
/useability Jester's Cap
/tell %t Jester's incoming
/2 Jester's on %t
/target_previous

Well, that's fine... he's trying to make a UI mod, not a macro. Macros rely on %t and the current target staying the same while UI mods can set the target statically without worry.

He just has funny ideas as to how to do the scripting. This would probably be better, but I cannot guarantee that Parent.Parent.GroupMember1.MemberInfoPage.Name.Text is the proper path for the text element without looking at the XML file.

path is ok for the cure buttons, that code is already in there.