Originally Posted by semlar
Check my edit, I got it working.
|
That sounds promising.
But I can't get your example to work. :/
I've tried that, and the new button just triggers the action that is on action slot 1.
btn:SetAttribute('summonmount', 268) is still ignored.
Could it be possible that the mount in question is on your action slot 1 and your new button just fires this action slot? Does the new button still work if your action slot 1 is empty?
It looks as btn:SetAttribute('type', 'action') without setting "action" to slot number uses a default value of 1.