Everyone should know what a release bot is or what it does but if you don't ill make a short rundown of what it does. A Release bot shows available software in the hub. It saves release names in a XML structure. Any ideas or input is really appreciated since improvement is a good thing for Direct Connect Network. I started sketching this idea for java since its the language i'm learning but don't be discouraged to submit your ideas or even example code in other programing languages since others can use it for other release bots or other software.
Here is a example of a current release bot
Current Release bots:adding example
<user> +add app "someappname"
<bot> User: <name> added "someappname"
listing example
<user> +list releases
<bot> <sends releaselist in pm or in main>
The New Releasebot
Well what a release bot needs is a XML Writer/Reader and a Parser
Got a tip from a friend about a XML Standard
http://www.xmlrpc.com/
These are the basic feats for a release bot should be pretty easy to do.
But i want to add some advanced features like
SFV Grabber
Well here is an idea i'm not sure of if its possible but thats what i use this forum for to get it explained for me. The idea is a users adds a release to the bot the bot then grabs the SFV file from that release and adds the data to a XML or something equivalent. Now u might be asking yourself why in the hell would anyone want this feature well this is to ensure that the "first" release that was added was a clean release untampered from the scene (common problem on Direct Connect Networks).
Request Thingy<user> +getsfv <releasename>
<bot> SFV Checksum for <releasename>
; Using hkSFV on 04.26.2008 at 08:59:16
; http://www.big-o-software.com
;
;/----
; 4745995 20:08.27 2008-04-22 example.exe
;\----
;
example.exe 1116e9d9
Another thing Spader enlighten me to was that request in release bots could use a fill function
an example of current requests in releasebots
Now Spaders idea was to have a fill function<user> +request "releasename"
<bot> user: <name> added a request <releasename>
Step 1
Step 2<user> +request add "releasename"
<bot> user: <name> added a request <releasename>
if a release name is filled in release list and found in request list then it should move from status unfilled to filled.<user1> +request add "releasename"
<bot> user: <name> added a request <releasename>
<user2> +request fill "releasename"
<bot> user: <user2> filled <user1> request for: <releasename>
Request list check
<user>+request list
<bot> <sends request list > unfilled and filled
ex.
<releasename> wanted by: <user> status: unfilled
<releasename> wanted by: <user> status: filled
Self Cleaner
The idea is that request unfilled or filled has a limited time in the list to old stuff don't add up there
so it should be time limited ex. 30 days etc.
Auto announcer
This Idea from Megatron
For those clients that support plugins to make a auto annoucer plugin.
Well this is all i got atm more ideas and thoughts is wanted from developers/user