Or else inserted_new is called for items newly added via a load command.

Inserted is always called when an item is added to the main downloads list.Īfter that, inserted_session is called when the source of that item is the session state (on startup),

Often starting with a digit, !, or ~, for ordering reasons. Note that practically all the events have pre-registered system handlers, d.size_bytes d.size_chunks d.size_files d.size_pex The new data is written to *.new files and afterwards renamed, if writing Only flushing the data in the *.libtorrent_resume and *.rtorrent files. Similar to d.save_full_session, but skips writing the original metafile, See also session.save and d.save_resume below. This writes all files that contribute to an item’s state, i.e. d.save_full_sessionįlushes the item’s state to files in the session directory (if enabled). If no bytes have been downloaded, the ratio is considered to be 0. This is the amount of uploaded data divided by the completed bytes multiplied by 1000. Returns the current upload/download ratio of the torrent. The possible settings (and the associated value) d.accepting_seeders d.accepting_seeders.disable d.accepting_seeders.enableĭ.priority = ‹hash› ≫ value ‹prio› d.t = ‹hash›, value ‹prio› ≫ 0 d.priority_str = ‹hash› ≫ string ‹name›Ĭontrols the priority of the item. Including when you delete or move it from the outside in a shell or cron job. One of the stop_untied, close_untied, or remove_untied commandsĬan then be used in a schedule to stop, close, or remove an item that lost its tied file, Leading to an empty value and the deletion of the tied file. (since the item is then loaded from there).ĭ.tied_to_file also starts out as the file the item is initially created from,īut can be set to arbitrary values, and an item can be untied using d.delete_tied, d.loaded_file d.tied_to_file d.tied_to_tĭ.loaded_file is the metafile from which this item was created.Īfter loading from a watch directory, this points to that watch directory,īut after a client restart it is the session file The try variants look at the d.ignore_commands flagĪnd thus only conditionally start/stop the item. On stop, incomplete chunks are discarded as part of the stop. Starts or stops an item, including everything that needs to be done for that.įor starting, that includes hashing the data if it already exists. TODO d.start d.stop d.try_start d.try_stop d.open d.close d.pause d.resume d.close.directly d.try_close See How Can I Stop All Torrents From a Shell? on how you can use that to influence the startupīehaviour of rTorrent. The three state values are persisted to the session, while active (paused) is not. Started items are both open and active, with state=1. Paused items are open, but not active, with state=1. Note that although pausing / resuming a started item does not change state, When that changed the last time, and how often it did change. These commands return the item’s state (1 = started or paused, 0 = stopped), It is also valid to pass no commands at all to d.multicall2, but all you get from thatĭ.state = ‹hash› ≫ bool (0 or 1) d.state_changed = ‹hash› ≫ value ‹timestamp› d.state_counter = ‹hash› ≫ value ‹count› d.is_open = ‹hash› ≫ bool (0 or 1) d.is_active = ‹hash› ≫ bool (0 or 1) To hold all the returned data serialized to XML. Make sure you set a big enough value for _limit If you request a lot of attribute values on all items, Only calling the commands for items that match it. d.name).ĭ.multicall.filtered is only available in rTorrent-PS,Īnd evaluates the predicate condition as a filter for each item, Typically, the given commands either just have a side effect (e.g. Or default when the view is omitted or empty.ĭownload_list always just returns a list of the contained infohashes.ĭ.multicall2 iterates over all items in view and calls the given commands on each,Īssembling the results of those calls in a row per item. These commands iterate over the content of a given view, ‘d.multicall.filtered’ is rTorrent-PS 1.1+ onlyĭ.multicall2 = ‹view›, ] ≫ list of lists of results ‹rows of results› d.multicall.filtered = ‹view›, ‹predicate›, ] ≫ same as 'multicall2' download_list = ‹view› ≫ list of strings ‹info hashes› d.multicall2 d.multicall.filtered download_list See the hint at the start of this chapter regarding the (sometimes implicit) target argument. The following are similar, but incomplete resources:ĭownload Items and Attributes ¶ d.* commands ¶

Mathmod scripts