Thread: Auctioning Plugin

This is a plugin I made to make auctioning loot a little easier.


If you are on Guk for example , there's a lot of people in the raid channel , but not everyone ... there's a lot of people in the 80-89 channel .. but some good buyers may be playing on their alts .. auction is a good channel , but nothing much happens on there so you're never sure if you have a target audience... Using all 3 of those channels to auction manually is a pain to say the least. This plugin offers a solution to these problems.

Also , if you have to concentrate on a fight , have to be monitor tells , structure the replies for the channels , make sure nothing goes wrong . All that adds to your stress level , wanting the auction to be over as soon as possible , rushing the auction .. even skipping the process all together for certain pieces. This plugin will make sure you can keep fighting , while the auction just goes on at the click of 1 button , you don't even have to type anything. It will get you and your guild more plat , and less headache.

How it works:

Fill in the main page of the plugin according to your server and guild's way of doing things. If you auction on multiple channels at once , just type in each channel separated with a comma.
Press Browse , to select a directory where the "Auction.txt" file will be created (be sure you have the right privileges in that directory) .

Make a do_file_commands macro in game that runs the Auctions.txt file that will be created.
If you take the screenshot as an example the command in the macro would be:
/do_file_commands C:\Users\zebulon\Documents\Auction.txt


To start an aucion in game you type /startaucion then link some item , then type a starting bid number and type in a zone. (order is not important) .
IE : /startauction [somebelt] 100 Underfoot Depths

Your client will of course say that /startauction is not a command it understands , but that's not important , it will be added to the log , and the plugin will pick it up.

Also , it _has_ to be a working link , you can verify that by checking the colour of it when your client reports the unknown command.

Once the auction is started you will hear a ding , that's your queue to press the macro the first time.

People will send you tells with numbers in them , every time you get a tell with a number that's higher than the highest bid , the "auction.txt" file will get updated to reflect that. When you press your same macro again , it will tell the channels what price the current bid is at. You don't _have_ to press the macro with every number you get , you can wait a few seconds to give people time to put in bids.

If you get no tells for a while , and press the macro again , it will say TWICE , then if you still get no tells with higher numbers it will say SOLD

If you get no tells back with bids at all it will go "muting once , twice muted" instead.

the last press gives a tell to guild with the price , and a tell to the guy that you sold it to. It will also finish the auction and give you a ding.


To stop the auction prematurely type /stopauction

If you have a funny guy that sends you tells with numbers that aren't related , you can set excludes on the first page of the plugin for people and for keywords like for example dollars or inches . You'll have to fine tune those for yourselves .

In case something did go wrong , you can always fix things by typing :

/setauction Playername 600

That will put the current bid at 600 for player Playername.

The triggers and responses tabs should not be changed unless you really know what you're doing , and have backups of a currently working configuration.

That's it for now.
Have a go , try it out , and report any bugs you find in this thread so I can fix them.

EDIT: You can use any custom channel to try out this plugin with a friend that's a pretend buyer.

Kind Regards
Dibbler.


Screenshot:
http://i762.photobucket.com/albums/x...es/Auction.png

Download

I've just installed a brand new act V3 with the auctioning plugin , to be sure that wasn't the cause.It is the only thing that changed since I last tested it. But everything seems to be running fine here.

Be sure , if you test with multiple accounts running from the same install dir , to only have the auctioning account with an active log (make sure /log is off on the other).

Send me a screenshot of the Main , Triggers and Responses tabs so I can check if everything is OK there. If you can , get me the xml file with your settings as well.

Try a /setauction 600 somename
and see if the auction / Auction.txt changes.

Check the Auction.txt file when you do a /startauction or press the /do_file_commands macro to see if the timestamp is correct.

Does the muting go through the whole muting cycle from once to muted ?

Be sure the guy is bidding more or equal to the price in the original tell ..

EDIT:
Try stopping and starting ACT just once right after you install the plugin . It might be a problem with internal variables not being inited when no config is loaded.

Glad it's working now , If anything else pops up do reply to this thread , I'll be happy to try and fix it.

Hey Dobs check your PMs

I am trying to set up the plugin in as well but I seem to be running into some issues advancing the script as well. My experience with programming is minimal and my experience with regular expressions is whatever ACT trigger I can look at and adapt to my own needs. Our guild does loot on an auction system internally I was looking to set up this plug in to work through a chat channel we set up exclusively for loot. I'm willing to bet there is a misplaced quote or period somewhere.

Minit: You tell %CHANNEL% \(.*\), ".* Starting bids at .*
Tells: \\aPC -1 (?<BUYER>\w+):.*\\/a tells sbauction , ".*
I'm fairly certain the issue is in the previous two lines. The channel I'd like to use is sbauction. I'm missing something in the triggers.

TRIGGERS
Once: You tell %CHANNEL% \(.*\), "Taking bids on .* Going ONCE"
Twice: You tell %CHANNEL% \(.*\), "Taking bids on .* Going TWICE"
Sold: You tell %CHANNEL% \(.*\), ".*Sold to.*for.* Gratz.*

MOnce: You tell %CHANNEL% \(.*\), "Taking bids on .* Mute ONCE"
MTwice: You tell %CHANNEL% \(.*\), "Taking bids on .* Mute TWICE"
Muted: You tell %CHANNEL% \(.*\), ".*Muted. Too late.*

Exit: You say to the guild, "Sold .* to .* for.*
ExitMute: You say to the guild, ".* up for transmuting.*

RESPONSES
FirstOut: csay %CHANNEL% %ITEM% Starting bids at %PRICE%

Initial Bid: csay %CHANNEL% Taking bids on %ITEM% %BUYER% %PRICE% Going ONCE
Second Bid: csay %CHANNEL% Taking bids on %ITEM% %BUYER% %PRICE% Going TWICE

Initial Mute: csay %CHANNEL% Taking bids on %ITEM% %PRICE% Mute ONCE
Second Mute: csay %CHANNEL% Taking bids on %ITEM% %PRICE% Mute TWICE

Muted: csay %CHANNEL% %ITEM% Muted. Too late.
Sold: csay %CHANNEL% %ITEM% Sold to %BUYER% for %PRICE% Gratz.

FinalMute: gu %ITEM% up for transmuting.

Final: gu Sold %ITEM% to %BUYER% for %PRICE%



So far I can start the script but I can't advanced it past the first out response. As you can see I tweaked a few of the lines to best suit our needs. I just also want to make sure that the once/twice count will broadcast not only the top bid but also the name of the top bidder. If this is not the case please let me know what I have to change to do that.

Fixed the Minit. Was missing the trailing quote....I hate programming

That tells line is still a mess though.

Well since you're getting there on your own , ill give you some more time before spoiling it.
Hint: you can't just chuck away variables that are going to be used later.

hmmmm... I get where you're going with that unfortunately this is where my lack of experience comes into play. I didn't save and now can't find the original text of that line so that variable that I chucked away is gone and I don't know how to rewrite it. The second hurdle for me is that I don't fully understand how regular expressions defines its variables so said variable may be in a later line but I first can't identify it much less use it. Maybe if I could have the original regex and a little hint at that variable.;-)

I do wanna get this working by tuesday night so if I don't get it off the next hint I may just ask for it flat out.