And what's wrong with that? Ludde's only got a finite amount of development time, and the whole point of the feature request forum is to find out what priority new stuff should have. If you post a possible feature and 200 people immediately jump on the thread and say "yeah, good one, I'd love that" then he'll prioritise it higher. If 50 people jump on a thread and say "you can do that anyway, via a->b->c, and besides, it's pointless because of xyz" then he's going to prioritise it lower. Whilst (as Firon said in another post) this is not a democracy, it's got to be helpful to the developer to know whether to spend time developing a feature which the majority of users want, and whether not to spend time developing a feature which is really just a workaround for a rare scenario and which isn't required because the functionality already exists - albeit via another mechanism. To be honest, I can't see why you'd need to regularly change the number of queued torrents anyway. If the torrents have enough seeders to max out your connection, then messing with the queue length won't download them any faster. And if you're having to increase the queue length so a particular torrent gets downloaded sooner because the others ahead of it in the queue don't have enough seeders, surely you can just hit 'Force Start' and away you go? I've been running bittorrent clients for years (and uTorrent for 3-4 months) and have never had to change the queue length once.