91 lines
7.2 KiB
Text
91 lines
7.2 KiB
Text
|
///////////////////////////////////////////////////////////////////
|
||
|
|
// Atma FileServer for mIRC 6.02+
|
||
|
|
// Version Information
|
||
|
|
// Confidential Developer Copy -- !!!NOT FOR DISTRIBUTION!!!
|
||
|
|
//
|
||
|
|
// KEY:
|
||
|
|
//
|
||
|
|
// + Addition
|
||
|
|
// - Removal
|
||
|
|
// = Planned Features
|
||
|
|
// [+x.xx] How much of a version change this will mean
|
||
|
|
// (at a guess)
|
||
|
|
///////////////////////////////////////////////////////////////////
|
||
|
|
|
||
|
|
[2.00-xxxxxxxx]
|
||
|
|
=Special trigger accts for loaded server modules, candidates listed below:
|
||
|
|
TDCC
|
||
|
|
XDCC
|
||
|
|
-- Will work as separate addons, but will require and intensely utilize Atma for all its server functionality, such as S/Q, Access, etc
|
||
|
|
-- Perhaps have spec. accts start with periods? (specifically, periods unaltered by the $trig.encode function, left invisible in atma config (optional maybe?), if visible, checkbox to set as a special acct (thus telling it to affix the leading period), or something)
|
||
|
|
Triggers..XDCC.!SylverScripts
|
||
|
|
Triggers..TDCC.!Rules
|
||
|
|
-- Maybe another serving system could be thought up.... would be great, but also difficult to come up with one
|
||
|
|
-- Use the proposed file transfer log as an atma module :)
|
||
|
|
-- Version 2 should, beyond any shadow of a doubt, justify ten-fold the arduous process of carefully coding atma for extensibility and scalability.
|
||
|
|
=Rebuild Atma dialogs using MDX in the most efficient and visually pleasing manner, perhaps adding additional dialog functionality in the process
|
||
|
|
=Whatever else comes to mind while developing 1.xx
|
||
|
|
|
||
|
|
[1.xx-xxxxxxxx]
|
||
|
|
=New Local Setting Overrides:
|
||
|
|
{ Trigger-Specific config options [+.05]
|
||
|
|
Trigger-Specific Send/Queue limit modifications [+.05]
|
||
|
|
Channel-Specific Ad Display Settings[+.05]
|
||
|
|
Channel-Specific Send/Queue limit modifications[+.05]
|
||
|
|
} -> Advanced Trigger config.... settings based by channel, * for all other chans (add/del/pick chan or * from a list)
|
||
|
|
User-Specific relative Send/Queue limit modifications i.e. +2 sends, -2 queues, +50% queues, etc. (to be added to fserv access list, access list will be optionally exclusive from that point on) [+.10]
|
||
|
|
=Automatic web-updating [+.05-.10]
|
||
|
|
=Multiserver support (perhaps using Network:#Channel, Network:Nick, or something to that effect). [+.10]
|
||
|
|
=Make queues persistant. Shouldn't be too hard, just requires queue management on fserv activation -- and, of course, not deleting the queue file when shutting down/starting up. Maybe let the user know files are coming first, though, if the queue's been offline for a while. [+.0x]
|
||
|
|
=File Transfer logging and management dialog -- keep track of what comes and goes, what fails, and who needs what. Could be good for trades too ;) [separate]
|
||
|
|
=Transfer Forwarding -- Allow users to specify a different nick to send files to, using NickChange principles
|
||
|
|
=Auto-backup of atma.dat after successfully loading it; allow easy restoration should it be found bad. Check for defaults when testing, i.e. Channels.*,
|
||
|
|
=Complete multiserver
|
||
|
|
=optional server-specific queue management over global
|
||
|
|
|
||
|
|
[1.30-20030131]
|
||
|
|
+Fixed !list bug -- since the 1.20 updates it was mysteriously tending to channels not being served to again.
|
||
|
|
+Fixed a queue bug -- users were able to queue one file over their limit. Not anymore.
|
||
|
|
+Clearing the queue file on Atma.Activate was moved to on:start, to keep it from deleting every time you joined a new server and had "activate on connect" checked.
|
||
|
|
+Fixed a bug in the CTCP trigger code. Nonconfigured channels were not detecting their CTCP requests properly. They are now ;o)~
|
||
|
|
+Changed how the access auditing timer was handled, so no more "ATMA.ACCESS.AUDIT Unknown command" errors
|
||
|
|
+Coded the rest of the buttons in the queue manager, also made sure they're all multiserver-compliant as well. No more buttons that don't work because the developer was lazy ;oP~
|
||
|
|
+Added a button to manually add a file to the queue. It was a useful feature some people thought would be a nice addition :)
|
||
|
|
+MULTISERVER ADDITIONS (Only basic activity, no multiserver configuration yet)
|
||
|
|
+Server ad now displays fine across multiple servers (it used to only work in the active server context, and barely at that)
|
||
|
|
+Queues now handled across multiple servers. (Stored the CID in the queue file)
|
||
|
|
+NICKCHANGE HANDLING
|
||
|
|
+When a user nickname change is detected, all of that user's queues are modified to point to the new nickname
|
||
|
|
+If a user changes their nickname with an active fserv session, that session is terminated to ensure that queues are not added using the old nick.
|
||
|
|
+Some minor tweaks to the code that I can barely even remember... mostly just to make sure everything works fine even when the $scriptdir contains spaces. Must support spaces.....
|
||
|
|
|
||
|
|
[1.20-20021205]
|
||
|
|
+Preview window now shows your ad using YOUR default channel font and size
|
||
|
|
+Integrated the Sylver Addon (SA) format specs
|
||
|
|
+Moved trigger style configuration to the Basic Config tab, under Ad Setup
|
||
|
|
+Moved QuickSearch settings to the Advanced Configuration tab
|
||
|
|
+Added session handling for fserv access (keeps track of whos on what trigger, typed it in what channel)
|
||
|
|
+Built in Channel Profiles -- the biggest addition this time around. This allows you to set channel-specific fserv settings, like ad settings and queue limits, for specific channels that override the global settings.
|
||
|
|
-- Queue limit checks are done using channel profile settings. Queues are passed to the fserv's global queue, there are no local queues, as they would only serve to hamper outgoing bandwidth.
|
||
|
|
+Let triggers contain spaces and periods (before this would cause weird problems, since spaces are not allowed in hashtables and periods are used as property separators, thus the trigger would not be added properly.
|
||
|
|
+CTCP triggers are NOW DEPENDENT ON THE USER BEING IN A CHANNEL THEY'RE BEING SERVED TO. This is to satisfy the requirement of a channel parameter in the session database for queue limits, so the fserv checks for an adequate channel that the user is joined to and uses that. Not perfect, but the best available for CTCP-style triggers. If no channel is found, the fserv is not triggered.
|
||
|
|
+Fixed a bug when deleting triggers,.. if the trigger being deleted matched the first letters of another trigger, the other trigger would be lost as well, i.e. deleting the trigger foo would also delete foobar, foob, etc.
|
||
|
|
+Made the QuickSearch cache process report total files cached / seconds it took / files per second... mostly just to satisfy my curiosity... its fast :D. good and exact too, used $ticks ^_^
|
||
|
|
+Made an installation script
|
||
|
|
|
||
|
|
[1.10-20021107]
|
||
|
|
+ !list now works even when fserv is disabled
|
||
|
|
+ !list no longer responds on channels not being served to
|
||
|
|
+ Triggers are now sorted alphabetically in the ad (some people really cared about this)
|
||
|
|
+ @find no longer responds if no results were found. Why flood users with queries if we've got nothing to sell?
|
||
|
|
+ Added support for people who type 'cd..' instead of 'cd ..' -- It was just irritating to watch
|
||
|
|
+ Gave Statistics its own tab to make room for more Advanced Config
|
||
|
|
+ When the fserv tells you to dccallow, it gives you the proper syntax now (it was up until now missing the '+' sign)
|
||
|
|
+ Added option to enable/disable in-fserv find
|
||
|
|
+ Added result limiting for in-fserv find
|
||
|
|
|
||
|
|
[1.00-20021017]
|
||
|
|
=+= First official release =+=
|
||
|
|
|
||
|
|
[0.00-20021007]
|
||
|
|
=+= Atma project started =+=
|