whitestarrising wrote:Original warden did not detect model-edits. I do believe that is considered a 'modified game client', though, so be careful.
|
![]() |
mrmr wrote:whitestarrising wrote:Original warden did not detect model-edits. I do believe that is considered a 'modified game client', though, so be careful.
Yes, original warden probably didn't.
Point is that on pserver, no matter what, it's not going to be the "original warder" running.
They're saying "model edit" will get you banned...but warden cannot "scan files".
So, how they will be able to catch original_MPQ_model_edit?
whitekidney wrote:I will not go into detail on how Nostalrius detects model edits but I can say it is the only server (ever) that I know of that detects client side model edits.
|
![]() |
mrmr wrote:whitekidney wrote:I will not go into detail on how Nostalrius detects model edits but I can say it is the only server (ever) that I know of that detects client side model edits.
...and you shouldn't.
I am just worried about these types of model-editing, as they're quite powerful&simple to achieve.
If you say these model-edits are detectable, then, kudos to the developer that wrote such warden module.
Askental wrote:gazi05 wrote:Hope it wont bother the devs here if we use it.
I am surprised they did not say anything yet, so yeah, I'm going to be the grumpy one... but I'm not really happy about these links and this topic being openly discussed here. I see that it might genuinely not be the intention in this case, but if you think for 5 minutes (or just browse deeper into this type of forum), you will find exploits using the same technique and I don't really want to see this spread on the server...
Personally I have nothing against a legit and verified pack of pretty textures, and this guy in your post seems alright but he is using different trees models... If it is just a tiny bit smaller than the default tree, someone else could see you walk right through it, and this can already get you reported, even if you did not mean to cheat... I would be extremely careful with this stuff, or just stick to what the engine is capable of without editing data.
|
![]() |