Jump to content

Implementing anti-cheat/db question


publiccert

Recommended Posts

Posted

Hi all,

I've finally got everything up and running. I had two questions:

Does anyone know how to implement anti-cheating? I've seen logs of other servers where admins are alerted in chat about speedhacking for example.

Also, I'd like general guidance on the DB process. I see many different releases in the update directory. Is it safe to say I should always apply ANY .sql files to my running realm? Which is to say, anytime a new .sql is updated in git, I should probably apply it? Also, I'm running two realms (release20, develop21). Is it safe to apply develop21 sql patches to release20?

 

Thanks!

Posted

As of a few minutes ago, Release20 and Develop21 branches are now merged !!!

Warden is a part of Mangos and has quite a few built in anti-cheating checks !!
- Just set it to active in the mangos.conf file

Posted

Very cool, thanks for clarifying! Can you clarify how I can tell if my DB is full 'updated'?

Also, how would I reproduce what I saw from a server GM. He showed me GM chat logs where speedhackers were generating alerts in chat. Thanks!

Posted

AS for the DB side of things.... the general rule is apply the installdatabases script, then apply any updates for the latest release
- Generally the install databases script also applies any updates for you

Posted
2 minutes ago, publiccert said:

Understood. So I don't need to apply Rel18/19 updates even though they're available in the repo?

That's correct, they are only available for those people upgrading from an earlier version.

The base DB is always on the current release

Posted

Thanks for clarifying that. It probably seems really obvious to you guys but I wanted to be overly verbose in case I miss something obvious. Do you have any thoughts on the anti-cheat feature I described?

  • 1 month later...

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy Terms of Use