Macro 1 yes /script ps= "promotional content"; sc = SendChatMessage
Macro 2 is /scriptt, f = t or 0, F or create frame ("frame") if x then print ("off") x = Nile print ("on") x = function () local t = gettime () if t-t > 60 then send chatmessage (PS, " channel ",nil,2)T = T end end end F:set script(" on update ",X)
In macro 2, 60 represents seconds, and 2 represents the number of channels. For example, if your trading channel is 4, change it to 4. Intermittent can also be replaced by words you are used to, such as the beginning and the end.
When using the macro 1, click it, and then click the macro 2. If it stops, click Macro 2 again.
If you want to insert clickable professional content into the call, please refer to the following.
1. code link macro: It must be used with the project ID. Just copy the macro below, and then change the ID and advertising language to what you want, and you can use it. The method of querying ID is in the appendix 1 below.
1. 1 single line display
/run local a,a = getitem info(22450); local b,b = getitem info(22446); Local c, c = getiteminfo (22449) sendchat message ("acquisition:" ... "220g/group ~" ... b "10g/group ~" ... c "1/kloc-0.
1.2 displayed separately
/2 acquisition:
/runlocala, a = getiteminfo (22450) sendchatmessage (""... a "220g/group", "channel", none, 2); Local b, b = getiteminfo (22446) sendchat message (""... b "220g/group", "channel", none, 2); Local c, c = getiteminfo (22449) sendchat message (""... c "220g/group", "channel", none, 2).
/2 Retail is also ok. Welcome to write.
1.3 shows acquisition+sale respectively.
This situation is also very common in actual transactions. How to make the three item links displayed in a macro include two items purchased by 1 or two items purchased by 1, where the purchase is one line and the sale is another? Actually, it's not difficult. Just combine the above two macros and modify them:
1.3. 1 buy 2 and sell 1.
/run local a,a = getitem info(22450); Local b, b = getiteminfo (25708) sendchat message ("acquisition:" ... "220g/group ~" ... b "100g/group, welcome mail, sold M~", "channel", nil, 2); Local c, c = getiteminfo (22446) sendchat message ("for sale:" ... c..." 130g/ group ~ mandatory m ","channel ",nil, 2).
1.3.2 acquisition 1, sell 2.
/runlocala, a = getiteminfo (22450) sendchat message ("acquisition:" ... a ... "220g/group ~ welcome mail, sell M~", "channel", nil, 2); local b,b = getitem info(22446); Local c, c = getiteminfo (29535) sendchat message ("for sale:" ... b "130g/group" ... "380g/m", "channel", none, 2).
* The current version has restrictions on the length of link fields, so unless "m stands for commodity [commodity] [commodity] [commodity] [commodity] for sale" is entered, only three links can be displayed, and the length of macro is limited to 255 bytes. So if you want to display more than four items, or if the advertisement is long and can only be divided into two macros, please adjust it yourself.
2 is a trading channel, and it can also be changed to 1 or 4, but you need to use the trading channel to display item links, and other channels only display white characters, so you can type and write directly when calling from non-2 channels (I am lazy, so I just copy the macro and change 2 to 4 or 1).
Special note: after copying my macro, the extra spaces automatically generated when the line breaks will be deleted. You must enter half-width English punctuation marks when editing the macro, or you will get an error.
2. Backpack link macro. Personally, I think code macros are more convenient, especially when I want to display what I don't have at hand. But for friends who edit macros, the backpack link macro is also a good choice:
/script G = GetContainerItemLink; M = SendChatMessagem ("acquisition:" .. G(4,1) .. "220g/group" .. g (4,2) .. "110g/group" .. g (4,3) ...
Pay attention to where you write the macro and put the item in that position. If the position is wrong or has not been changed, there may be a message: "Hearthstone is for sale [220g/group ~", which will be embarrassing ~ Hmm ~ I was stared at twice with disdain when debugging this macro.
Pay special attention again: after copying my macro, the extra spaces automatically generated when line breaks are deleted, and you must enter half-width English punctuation marks to edit the macro, otherwise you will get an error.
Appendix 1: Method for inquiring the ID of an article
The item information plug-in that comes with the Warcraft Elf (I believe there is a similar plug-in in bigfoot, but I haven't used bigfoot and don't know much about it):
RatingBuster plug-in, if you want to know if you have this plug-in, click /rb win, and the setting method is as follows:
According to the library, you can also query items.
Appendix II: Adding Skills in Hong Xiang
I found that quite a few friends don't know how to add skill links to macros, so I made this appendix II to explain it by the way.
General occupation skill increase method: Open the skill page, there will be skill name and a yellow chain, open the macro editing cursor and put it in the position of the advertising language, and SHIFT+ left mouse button click this chain to directly increase the skills for the advertisement:
The method of adding a single skill is the same. For example, write [Enchant: XXX], click on this skill page and macro edit, and SHIFT+ left click on the skill.
It is worth noting that the total skill link can only have one macro, which takes up one item link ~ so please make up two macros to call two professional friends. A single skill link macro can have multiple item links, but a macro can only display three item links ~ so if there are more than three, please make up two macros.
The following macros are for friends who use skill links and friends who only shout 1-2:
Contains 2 project links.
/run local a,a = getitem info(22450); Local b, b = getiteminfo (22446) sendchat message ("acquisition:" ... "220g/group ~" ... b "10g/group ~ retail is ok, welcome email", "channel", nil, 2).
Contains 1 project links.
/runlocala, a = getiteminfo (22450) sendchat message ("acquisition:" ... a ... "220g/group ~ retail is also acceptable, welcome email", "channel", nil, 2).