New or cleaned MatchBot

[Maverick]

I couldn't find a ticket for this so I decided to make a new one. (Close this one if there is already a ticket about this.)

Basically a cleaned version or a new MatchBot is required;

• Contains all the features of current MatchBot. (Can host TWDD, TWJD and TWBD.)
• Clean Matchbot code-wise
• Lots of javadoc and code comments
• Clean separation of mysql queries in the code where only ONE database source is used (might require database change).
• Configurable but an example configuration containing all the possible settings and for each setting a comment what it is
• ...?

Note; a seperate bot will be made for the base/wbduel/javduel games. Ticket #238

[milosh]

I never really got any feedback on the cleaned matchbot.java code I sent you. Would you like me to remake the entire bot in that style? It's not so much reinventing it as cleaning it out. If so I may be willing to incorporate the Power Ball Bot into it. Let me know.

[anonymous]

Could you add a command which allows you to see the resolutions of other people in the arena? Something like !res playername and then the bot sends you back the resolution of that player. If 1440x900 resolution is going to be allowed it's only fair for people to know who is using it and who isn't.

[Maverick]

Anonymous, I don't see that as a really necessary feature right now.
Whoever is going to create this bot can do it when he's working on it but it's not important enough to put it as a requirement.

[milosh]

Going for consistency.

[fantus]

I got an idea for hosting TWD matches:

- one hub bot that manages all the challenges and matches.
(People can still !challenge from the child bots, but the challenges get handled by the hub bot.)
The hub bot will include the current twdbot functions.

- child bots host the matches and pass the challenge commands to the hub bot

Other idea's:
- There is no reason why a childbot should stay on. For example when a child bot has not hosted for lets say 30 minutes, it disconnects. People can still challenge through the hub bot. When all the current childbots are busy a new one will get spawned and appointed to host the match in a free arena. This way we can reduce the amount of idle bots in the zone.
- Limit challenges per challenged squad to 1, no more challenge spamming from different arenas.

Tickets that will be solved once it's done:
#210
#343
#318
#331
#205 (?)
#253
#267
#316
#312

[Maverick]

That's a great idea, fantus.

I would make the restrictions between the hub and the clients a bit more tight though;

• People can only !challenge on the TWDBot
• A child bot is only spawned when it's hosting. It disconnects as soon as the match is done.

This idea would certainly solve the problem of having not enough Matchbots on for one type of TWD and, indeed, reduce the amount of idle bots in the zone.

Do you know how the !challenging goes? I thought the bot challenges another squad and waits for a response (for acceptance or denial). If you can only challenge a single squad, wouldn't it be very cumbersome to find a TWD match (challenging, waiting for a response, challenging, etc) ?
Making a list of squads that are searching for a match for a specific TWD type would be a better idea?

[fantus]

Think you misunderstood me on the 1 challenge allowed part: Sometimes you get multiple challenges from the same squad. For example "Squad 1" challenges my squad from twdd and twdd2. This will no longer be allowed. Only one challenge from "Squad 1" will get processed. In the main time "Squad 1" can still challenge other squads as well.

The ticketlist includes some tickets that improve challeging in general, for example challenge all top 5 squads. Or challenge a range of squads with the same rating as your squad.

The hubbot will also keep track of a list of squads that just challenged, so others can see with for example !looking what squads are looking for a game.

[Maverick]

Yes I misunderstood you (plus I don't know how the !challening works) :P

Anyway, good stuff