; on the rush side of things you need to make a bookmark to all your predirs on your sites, and call
; the bookmark pre
;
; you also need rushmirc.dll in your mirc dir, and mirc needs to be restarted. you need the tmuk
; version of the mirc dll. It's available from the registered users area of the ftprush forum.
/pre {
/dll rushmirc.dll SetMircCmd /parserushpreoutput
; this line makes rush log into all your sites. have as many as you like here, but separated with a semi-colon
/dll rushmirc.dll RushScript RushApp.FTP.login('SITE;SITE2;SITE3','pre',RS_BOOKMARK);
; This next line needs to be recreated for each site. The name of the site, the pre command for each site,
; and the name of the section. Instead of the release name, there must be $1 - the release name is
; passed to this function when you execute the pre command in irc.
/dll rushmirc.dll RushScript RushApp.FTP.RAW('SITE','site pre $1 TV-XVID',RS_LOGIN or RS_LOGOUT);
; so you might want to add:
;
; /dll rushmirc.dll RushScript RushApp.FTP.RAW('SITE2','site pre $1 TV',RS_LOGIN or RS_LOGOUT);
}
/parserushpreoutput {
; this part's a little more complicated to edit. when a raw command is executed from mirc, it'll send whatever the
; ftp says as a reply back to mirc. you need to parse this feedback to confirm if the release pre'd ok or not.
; depending on the pre script the site uses, it can be tricky to decide what words to look for to indicate a
; successful pre.
;
; the first token mirc will receive is always the site's name, according to the rush bookmark.
;
; in this instance, the site replies:
;
; (SITE) 200- /site/pre_releases/_PRE/Group
; (SITE) 200- --- f00-pre v3.3+ -------------------------------------------------------
; (SITE) 200- * Looks like this is going to be a Group pre..
; (SITE) 200- * Destination for pre will be the tv section..
; (SITE) 200- * Totals of this pre for announce: 49F 732910656B
; (SITE) 200- * Moving files to destination dir..
; (SITE) 200- -- From: /site/pre_releases/_PRE/Group/Release-NAME
; (SITE) 200- -- To: /site/tv/Release-NAME Done
; (SITE) 200- * Updating userfiles ..
; (SITE) 200- -- *username*: No stats given, Credits: 2130.5 Mb, Ratio: 3 (s:0)
; (SITE) 200- -------------------------------------------------------------------------
;
; so we can see that the 8th line is the line in which the site confirms the rls has pre'd.
; specifically, we need to check that the first token is (SITE) (whatever the site's called)
; and that the second token is 200-
; and that the third token is --
; and that the fourth token is To:
; and that the sixth token is Done
;
; if the bot never says a line that fulfils these requirements, then you know something's gone wrong. ;)
;
; this will be different for each site you're on, so this bit will take a while to customise.
; so these next 3 lines, you'll need a copy of them for each site
if ( $1 == (SITE) && $2 == 200- && $3 == -- && $4 == To: && $6 == Done ) {
/msg #channel # Release pre'd on SITENAME!
}
}