thanks for reporting

Pool mining available on Rplant with SRBMiner:

V2.5.2
+ Added algorithm 'randomscash' [Satoshi Cash] for CPU mining, fee 1.00%
+ Performance improvement on algorithm 'fishhash' for AMD Rx400/500 GPU's

V2.5.1
+ Added support for AMD BC-250 Mining GPU's
+ DevFee for 'fishhash' algorithm lowered to 0.85%

V2.5.0
+ Added algorithm 'fishhash' [IronFish] for GPU mining on AMD/NVIDIA/INTEL, fee 1.00%
+ Added support for dual mining FISHHASH/BLAKE3_ALEPHIUM on AMD RDNA/RDNA2/RDNA3, NVIDIA and INTEL GPU's
+ Added support for dual mining FISHHASH/BLAKE3_DECRED on AMD RDNA/RDNA2/RDNA3, NVIDIA and INTEL GPU's
+ Added support for dual mining FISHHASH/SHA512_256D_RADIANT on AMD RDNA/RDNA2/RDNA3, NVIDIA and INTEL GPU's
+ Added support for dual mining FISHHASH/PYRINHASH on AMD RDNA/RDNA2/RDNA3 and INTEL GPU's
+ Added support for mining 'yescrypt' algorithms on AMD gfx1100 GPU's (RDNA3)
+ Fixed dual mining of AUTOLYKOS2/PYRINHASH on INTEL ARC GPU's
+ Auto setup (threads/affinity) for 'yespower' and 'yescrypt' algorithms on CPU should now work better
+ Removed support for AMD RX550/560 GPU's
+ Removed algorithm 'blake3_ironfish'
+ Removed algorithm 'xdag'
+ Removed parameter 'gpu-progpow-preload'
+ Minor bug fixes

***
Known issue: RX400/500 - algorithm 'fishash' on Windows has low hashrate compared to Linux.

V2.4.9
+ Added support for GPU mining algorithm 'meowpow' [Meow coin] on AMD/NVIDIA/INTEL GPU's, fee 0.85%
+ Fixed possible invalid shares on PROGPOW algorithms [AMD Ellesmere GPU's]
+ TLS/SSL pool connections now supported over socks5 proxy (--proxy parameter)

***
- You will probably experience weird GPU behaviour (hashrate drop, stop hashing for a few seconds) on 'meowpow' algorithm on the testpools, until MeowCoin actually switches from KawPow to this new algorithm. (Mar 18. 2024)

Exactly. There are also blog's where the link to the miner is NOT from the official github repo.

Download only from the official github repo [ https://github.com/doktor83/SRBMiner-Multi ]

V2.4.8
+ Added support for mining PROGPOW algorithms on INTEL GPU's [kawpow, firopow, progpow_epic, progpow_zano]*
+ Added support for GPU mining algorithm 'aurum' on AMD/NVIDIA/INTEL GPU's
+ Added support for dual mining ETHASHB3/SHA512_256D_RADIANT on INTEL ARC GPU's
+ Added support for algorithm 'heavyhash' on AMD VEGA GPU's on Linux (ROCM)
+ Performance improvement on PROGPOW algorithms on AMD/NVIDIA GPU's
+ Performance improvement on algorithm 'aurum' for CPU's
+ Returned support for mining algorithm 'cryptonight_ccx' on CPU and AMD GPU's [ UltraNote Infinity coin ]
+ Setting any cclock or mclock OC parameter's value to 0 will now reset the value of core clock / memory clock to the default value
+ Fixed broken DUAL AUTOLYKOS2/BLAKE3_ALEPHIUM on some AMD RDNA2 GPUs
+ Fixed a bug with 'autolykos2' that could cause bad dataset creation (invalid shares)
+ Fixed a bug with nonce distribution for algorithm 'randomepic' on EpicMine pool
+ Removed parameters and functionality for : '--gpu-buffer-mode', '--gpu-disable-auto-buffer', '--max-difficulty', '--start-block-height', '--gpu-autolykos2-preload', '--multi-algorithm-job-mode', '--gpu-auto-tune', '--gpu-ethash-mode'
+ Linux releases will be packed with tar.gz from now on [ not tar.xz as before ]

***
- GPU auto tune feature (former --gpu-auto-tune parameter) is now enabled by default for every algorithm. Manual override is possible with '--gpu-intensity' parameter.
- Miner will auto-detect if '--multi-algorithm-job-mode 3' is needed (currently algorithms : randomepic, progpow_epic), so the functionality of algorithm switching is preserved, and no user action is needed anymore.
- On INTEL GPU's there can be issues with PROGPOW algorithms (invalid shares) if the coins DAG size is bigger than 4GB. This will be fixed when Intel decides to fix it in their driver.

nah, its easier for everyone if you just stop being a douchebag.

V2.4.7
+ Performance improvement on algorithm 'aurum' for AVX2 supported CPU's
+ Fixed broken 'yespower' algorithms
+ Fixed broken algorithm 'blake3_decred'
+ Fixed broken --gpu-coffset and --gpu-moffset parameters (Linux)
+ Added parameter '--cpu-numa-bind' which can force binding of CPU worker threads to a specific NUMA node (per algorithm)*
+ Default --esm (ethereum stratum mode) value for algorithms 'ethash' and 'etchash' is now 2 (EthereumStratum 1.0 + nicehash mode)
+ Renamed parameter 'disable-numa' to 'disable-numa-binding'
+ Minor bug fixes


--cpu-numa-bind

Bind CPU worker threads to NUMA node id 1 (second NUMA node) with auto thread selection and affinity mask:

Bind CPU worker threads to NUMA node id 1 (second NUMA node) with manually set number of threads and affinity mask:

Because he would be already banned there with this attitude..  

Insane. Did you actually cared to fix the TYPO you have ?


vs fixed:

cared to fix that ?

--multi-algorithm-job-mode 3 is not broken, also its not a gpu dependent thing. Write down the example that's not working for you, then i might be able to test.

Im aware of some yespower derivates broken - broke in last version - not for very long time as you wrote.
Also the miner vs pool hr on some algorithms fixed in v2.4.5 - it is in the release notes.

You could be kind enough and write down here those bugs ?


Try add --esm 2

edit: tried --esm 2 and 2miners etc with latest version, found shares were registered on poolside. So its working as it should.

Tested both on herominers pool and its ok.
So please provide more information.

V2.4.6
+ Added algorithm 'aurum' (BitNet) for CPU mining, fee 2.00%
+ Minor performance improvement on algorithm 'blake3_alephium'
+ Added support for algorithm 'cryptonight_turtle' on AMD gfx1100
+ Added Vega56/64 rocm binary for algorithm 'cryptonight_turtle'
+ Minor bug fixes

V2.4.5
+ Minor performance improvement on algorithm 'karlsenhash' for AMD RDNA2 GPU's
+ Minor performance improvement on algorithm 'sha3d'
+ OC parameters (NVIDIA) should now work as expected on both WINDOWS and LINUX
+ Fixed issue with lower poolside hashrate on algorithm 'blake3_alephium' introduced in previous version
+ Fixed an issue that caused higher difficulty to be used than what the pool sent - on some algorithms, introduced in previous version
+ Removed algorithms : blake2b, blake2s, yespowerlitb, yespoweriots, yespoweritc, yespowerres, yespowerarwn, cryptonight_talleo, cryptonight_ccx, randomhash2, scryptn2, k12, keccak, dynamo, minotaur, kaspa

You are right about MinotaurX. About the broken devfee pools, which ones?