• [FEATURE REQUEST] Working macros

Posted: **Thu Feb 07, 2008 9:50 pm**

Not more important than most things, but for in-game development, Macros are a must. The shift/alt arrow buffer in chat doesn't work most of the time, and re-typing /move_spawn or other spawn fixup commands gets tedious after 200 or so.
How intense is hooking these macros up, and is anyone savvy enough to help LE with this? I can take a look, but I definitely am a novice at C++.
Thanks,
-J

Posted: **Thu Feb 07, 2008 10:27 pm**

I don't understand what you are asking for. Could you explain in more detail.

Posted: **Fri Feb 08, 2008 3:35 pm**

heh it would be trivial to setup. Just like friend/ignore lists it is simple to setup, I just haven't gotten to it yet. I'll add it after I fix the death code. If you want you could help me out by adding the table.

Posted: **Sat Feb 09, 2008 10:59 pm**

Ok, I'll see if we can come up with a Macros table. I guess it's just a simple title / text and some ID?
I hadn't thought of that part, thinking macro text is stored at the client. But that might have been EQ1.

Posted: **Sat Feb 09, 2008 11:02 pm**

Nope, the server sends the macros to the client when they login. That way you can access your macros on another computer without problems.

Posted: **Sun Feb 10, 2008 12:51 pm**

Actually, looking at Alfa's proposed structure, it looks like he already made some considerations for Macros.

Code: Select all

CREATE TABLE `character_macros` (
  `id` int(10) unsigned NOT NULL auto_increment,
  `macro_id` int(11) unsigned NOT NULL default '0',
  `name` varchar(64) NOT NULL default 'macro',
  `char_id` int(10) unsigned NOT NULL default '0',
  `type` enum('COMMAND','ABILITY','EQUIP ITEM','USE ITEM') NOT NULL default 'COMMAND',
  `text` text,
  `order` smallint(5) NOT NULL default '0',
  PRIMARY KEY  (`id`)
) ENGINE=MyISAM DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ;

How does that look? Any other fields we might need for macros? Slot ID maybe?

Posted: **Sun Feb 10, 2008 12:56 pm**

Btw, I just had an excited panic attack thinking macros already worked - cuz I made a few, macros in-game, ran around using them and they worked!
(I love the new macro building functionality - hadn't seen that before. RoK client?)
However, sadly, when I log and come back, they are gone. So yes, we'll need a way to store them.

Posted: **Sun Feb 24, 2008 12:08 pm**

Feature Implemented. Request can be closed!