You don't understand nothing lol. Orpheu, is like fakemeta, engine, etc. It's just another module with provided natives to do some things. So module is used only if a plugin uses this module. Orpheu will be used more and more because you can do now a lot of things more efficiently by executing/hooking directly CS functions or from another libraries or patching memory. It's clear you have no idea how this module is extremely powerful. Which is funny is you compare the size dll, it's totally irrelevant. A bigger module doesn't mean more cpu eaten.
Quote:
|
I thought maybe you could have said that orpheu is that much better coded that although it's a giant module (3 x bigger than this one) it still causes less RAM or CPU usage than this module and sowith would be less "heavy" on HLDS.
|
You still say such thing. You really don't know what you are talking about. Both modules don't do the same thing. This module search into the memory all value which match 16000 without checking if this value is used for money... That's why you get a weird noise because some value should not replaced and used for another thing. Orpheu is more dynamic since it does more thing, using a plugin I do the same thing as the module but the difference it doesn't search the value 16000 ; it alters values at known place and mp_startmoney can be between 0 and 2147483583. ( this module only 800 to 999999 which is the max value that the hud can show )
Please don't try to argue with CPU/RAM if you don't know how it works. It's totally irrelevant there. Even if the orpheu native to alter memory uses more code thus a slightly more the cpu, you are trying to argue for something which will be executed one time and where the difference is trivial because you will notice no difference. -_-
If the module was doing the job properly and safely, for sure I would recommend to use it since it matches to your need, but that's not the case.
Anyway do what you want. I was just answered to your wrong assumption.
but in memory
Linear Mode
