Posted February 26, 2010 Hi, there is bug with alternate speed limiter. The values are switched. For example if you set alternate speed for upload to 1000kB it will set this speed for download and vice versa. Share this post Link to post Share on other sites
Posted March 2, 2010 Hi, there is bug with alternate speed limiter. The values are switched. For example if you set alternate speed for upload to 1000kB it will set this speed for download and vice versa. This is fixed in 1.3.1. :D Share this post Link to post Share on other sites
Posted March 6, 2010 limiter's value no longer included in tag ? it prevents hub from kicking users with too low limits, doesn't it ? Share this post Link to post Share on other sites
Posted March 6, 2010 limiter's value no longer included in tag ? it prevents hub from kicking users with too low limits, doesn't it ? Read change log for StrongDC 2.40 ^_^ Share this post Link to post Share on other sites
Posted March 7, 2010 limiter's value no longer included in tag ? it prevents hub from kicking users with too low limits, doesn't it ? Upload limit is included in connection field where it is more logical. Share this post Link to post Share on other sites
Posted March 7, 2010 Upload limit is included in connection field where it is more logical. logical it is, but it makes preventing users from using too low limits more difficult.. Share this post Link to post Share on other sites
Posted March 7, 2010 No, it doesn't. The only difference is the used field. Share this post Link to post Share on other sites
Posted March 7, 2010 No, it doesn't. The only difference is the used field. it definately doesn't work on dbhub. yes, it's outdated and no longer supported, but works better than verli with much plugins. well, nevermind. Share this post Link to post Share on other sites
Posted March 7, 2010 it definately doesn't work on dbhub. yes, it's outdated and no longer supported, but works better than verli with much plugins. well, nevermind. The use a client to do the job... that can be done easily. Share this post Link to post Share on other sites
Posted March 8, 2010 If it doesn't work in some hub, it means that such hub isn't properly configured to read connection field. It is hub bug in most cases, because connection field is standard part of protocol command in contrast to tag which is ignored (and not to sent to users) by many hubs. Share this post Link to post Share on other sites
Posted March 10, 2010 The use a client to do the job... that can be done easily. good idea, thanks :angry: Share this post Link to post Share on other sites
