First and Foremost : Thanks to all those that continue to make EGGDROPs possible.
I use my eggy as a trigger bot file server and have yet to experience any problems what so ever.
I now wish to allow chanops to update a file without allowing them access to the eggy. The only thing preventing such is (best I can determine) eggys don't support "accept and overwrite" as an option under DCC file transfer. Currently I use a !trigger to remove/delete the exsisting file prior to uploading. Most forget to use it, therefore preventing uploading.
The exsisting file name must not change in order for the !trigger to function.
Does anyone have an idea how to set the eggy's DCC get mode to "Accept and Overwrite"?
guess you could just upload the files to a different dir (like filesys/incomming/) and then do a do a check to see if the file exists, before copying it to the right place.
should be easy enough to make a tcl script automating it.
My goal is : I now wish to allow chanops to update a file without allowing them access to the eggy.
Road Block is : The exsisting file name must not change in order for the !Trigger to function.
An example : Let's say !TodaysNews is the trigger to get a file with "today's news". Obviously in order to keep such a file current it's contents must be changed daily. Without allowing bot access such a task lies upon me. If dcc to bot would accept and overwrite exsisting file names update duties could be delegated to others without allowing them access to the Bot or shell.