![]() * Custom control over the polling rate for optimal performance. * Optionally displays popup alerts when AutoPilot terminates a seed. * Optionally suppresses termination when seeds are force-started. * Optionally terminates seeds when queuing incomplete torrents. * Optionally deletes the torrent file upon removal. * Optionally removes the torrent when seeding is complete. * Maximum swarm seed conditional which ends seeding when met. * Minimum swarm seed conditional which forcefully suppresses termination when unfulfilled. * Ratio Quotas that define a torrent's maximum share ratio. User-defined values newly added torrents with a matching tracker inherit its settings from. User-defined values newly added torrents inherit its settings from. * Manages individual settings for each torrent. Complimented by an advanced default & tracker override system, users may feel at rest knowing they are contributing back to their community exactly the amount desired. ![]() Trackers will automatically be removed from the All Trackers view when they haven't been in use by any torrents for a while.AutoPilot is a plugin module for the java BitTorrent client BiglyBT ( ).ĪutoPilot manages seeding by allowing users to place individual ratio quotas on every torrent. ![]() This can result in tracker entries in the view that have no associated downloads as they have been redirected to an alternative. If you find that trackers re-appear after being removed then this might be due to DNS Tracker Preferences - make sure that you remove all trackers for the given domain. A strict definition of how multiple trackers should be handled is available ( although few clients, if any, rigidly adhere to this. This does not mean they are dead - they may well be required in the future. When a tracker is queued there are no online/offline statistics available which is why some trackers will not have data available. This is why you will see some trackers in a 'Queued' state. Not all of a download's trackers will be consulted for peers, especially if the download has 'enough' peers from other sources. This will result in all current and future downloads being automatically assigned to the tag and having the selected trackers removed. This is the same as the above 'remove from current' except that it assigns a tag constraint of 'true' to the tag rather than assigning the existing downloads. Remove from current and future downloads: It then assigns all your existing downloads to that tag which will result in the selected trackers being removed. This creates or re-uses a compatible tag and tracker template and configures the tag to use the template for 'removal' purposes. This then shows which of your current downloads are using the given tracker(s) This allows you to quickly create a new Tag/use a compatible existing Tag and assign tracker properties to it consisting of the selected tracker(s). Within the All Trackers view you can select one or more trackers and use the right-click context menu to perform actions on them: Tracker Templates can be used to automate the addition and removal of trackers to downloads when they are assigned to a Tag. Tracker Properties can be used to automatically assign downloads containing given trackers to the Tag. Existing ControlsīiglyBT has some existing features for managing trackers based on Tags. However it can be hard to get a global view of the trackers being used by BiglyBT - hence the introduction of the 'All Trackers' view accessible from the 'View' menu. Over time these dead trackers can accumulate and waste BiglyBT resources as attempts are made to communicate with them.Įach download has a 'Sources' tab that shows the current state of the download's trackers (and alternative peer sources). These trackers have varying stability and often go offline permanently. Each download uses one or more trackers to obtain information about other peers that are downloading/seeding the same torrent.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |