Topic: Possible Adition to !raid add <nick>

[Solerna]

Running a raidbot that so far has been a flatroll bot has kinda let me avoid this problem. But the goal with it was to make a better bot and if wanted one with points. And I'm soon facing a vote in regards to having points or not. So at this points this is just theries and ideas.

During a raid where items are bidded on and points are given for acheiving different goals there is always a risk of ppl  leeching, thus the !raid add or whatever command is used. Usually this jobs is apointed to a Raidleader. But Doing !raid add <nick> on 100+ ppl (imaginary figures, we have had 75 as most so far I think) is a pain, takes time and spams the bot like... Letting ppl !raid add themselfes isn't an option. So what alternatives do we have?

!raid add <nick>
needs to be spammed alot, Ctrl-tab and quick fingers will do it.

!raid add all
Ouch >.< Beware leechers are comming.

!raid add "me"
Same as above leechers galore

None of these apeal to me verry much. So I've wondered if there might not be some other way to do it.

What came to my mind was this:

Step1:
Module. Creates a list of all ppl in bot sending them to the raidleader as a Blob in the formate "/assist person1" newline "/Assist person2" newline and so on.

Step2:
Raidleader quickly copys this to a script in the ao folder. and runs it.

Step3:
The raidleader will not get back something like this:
Can't assist yourself.
Can't find target person2.
Target is not in a fight.

Step4:
Raidleader quickly copies this and sends it the bot with some neat command: "!raiders Can't assist yourself. Can't find target person2. Target is not in a fight."
making the the bot go "AHhh! =)" Automaticly raidadding all that got no errors.

This can't work alone, errors do happen, someone was to far away. Someone wasn't there yet and so on. But it aught to make it easier on large raids.
And with the adition of still being able to use !raid add <nick> I'm wondering if this might not be something. In my case its for an alien playfieldbot.
With that in mind I know that once the gates are closed no one more can join. If they are not in zone by then. They have missed the raid, no exceptions.

Comments pls =)
What flaws does my Idea have, can it be improved?

[Khalem]

imho, that sounds like more work than the current !raid check which works quite well and doesnt take long to complete even for a 100+ raid.
Theres also the issues with the chatsocket limitations in terms of how long messages can be and how many messages can be sendt in x seconds etc, and for any large scale raid, the raidleader would with your suggested approach need to flood the bot, not to mention he would himself get flooded badly from the script.

[Solerna]

On a 100 man raid u would have to make 4 /assist macros containing 25 names each.  chat system could handle about 30 but 25 is safe. (I got long messages)

The response would be this(per 25 atemptes assist, with different names though, and target no in fight for those being there):

Can't find target >Solerna<.
Can't find target >Bobbo<.
Can't find target >Solerna<.
Can't find target >Bobbo<.
Can't find target >Solerna<.
Can't find target >Bobbo<.
Can't find target >Solerna<.
Can't find target >Bobbo<.
Can't find target >Solerna<.
Can't find target >Bobbo<.
Can't find target >Solerna<.
Can't find target >Bobbo<.
Can't find target >Solerna<.
Can't find target >Bobbo<.
Can't find target >Solerna<.
Can't find target >Bobbo<.
Can't find target >Solerna<.
Can't find target >Bobbo<.
Can't find target >Solerna<.
Can't find target >Bobbo<.
Can't find target >Solerna<.
Can't find target >Bobbo<.
Can't find target >Solerna<.
Can't find target >Bobbo<.
Can't find target >Solerna<.

This much can be sent a once without riksing to exceed the send limit.


Saving that as an array. splitting with the "." Removing all "target not in a fight" and Can't assist yourself.  Doing a substr($msg, 20) to remove the start and so on. Leaving u with an array of names that could not be assisted.

If this was used only to check if ppl were there, the need to send it back to bot would be little, but I inteded this to work as a !raid add at the same time as checking if ppl are there. And that by adding all pll in bot to the raid that could be assisted.

The raidcheck u sugested mean I have to click on everyone atleast once to see if they are there. This does 25 per go. (could do more but then one would have to count when sending to bot). just pasting the reply to the bot and make it act upon the result.

I'm not sure this will be more work. But there will be no flooding of the bot. On a 100 person raid I can send back all the assists in 4 tells.  So bit it long tells, but still just 4 tells. 25 assists in a script takes about 2 secs to perfom for me.

In essence what it would do would be to raid add and raidcheck at once.

[Solerna]

Played around with it a bit. I was wrong about having to copy and paste  the /assist nick parts in a script.
One can just as well have the bot create a macro in the form "/macro ass /assist nick1 \n /assist nick2 \n /assist nick3" and so on. It actually does the trick. =)

[Khalem]

Never mind me. I shouldnt be posting in the small hours

Yes, it could actually work. Let me know how it works out

[Aiiane]

Seems like overkill though - one handy tip I've found when it comes to checking active is that /assist has a slightly odd behaviour that you can take advantage of - "Target is not in a fight." messages go to whatever window has System subscribed, but the "Can't find target >Name<." messages go to whatever the default chat window is. If these are separate windows, then you can just look at the default window and easily read off the people who aren't there.

So perhaps it would just be enough to have the large /assist macro, and then manually kick those not present a la !raid check.