ESL Autumn Season Rule Update!

5 Comments • Posted By aKaaa at 2011-10-24 22:44 CEST • Hits: 957

Rule Update

Recently, it came to light that the command db_status was not working in the correct way, it was bought to the attention of the developer of the plugin. However, he tried to fix the bug but it seems this issue can not be fixed in time for the new season of the ESL Autumn Season. Therefore the admin's have decided that it's necessary to add the old rcon status back into the ruleset.

Please beware that the rule shall be enforced from Tuesday 25th October. Here is the amendment to the rule set.

2.1 Screenshots

Both parties are responsible for uploading a screenshot of every played round in matchmedia. You also have to take a "rcon status" and "db_info" screenshot, but only the team/player who provided the server is responsible for taking them. All screenshots have to be uploaded to the match page within 24 hours after the match. If you failed to upload them in time you can also write a support ticket and the ESL admins may delete the penalty points given.

For taking a valid rcon status + db_info screenshot you have to write the following commands into console:

rcon_password XXX
clear (to hide your rcon_password)
db_info
rcon status
jpeg

To make sure you are up to date with the rule changes in this seasons event, please check HERE or post a comment, someone will be sure to answer you!

Name: Aaron "aKaaa" Swain
Age: 25
Location:

United Kingdom

Avg. Rate:

0 / 10
( 0 Votes )

Comments[Goto Last Comment]

Post Comment

1 So1o 2011-10-25 00:06:10 CEST

thx Aaron

2 brnii 2011-10-25 20:50:05 CEST

So, how come clutchmasterz got a warning from ESL when we didn't take a "db_status" shot when we didn't provide the server?

3 So1o 2011-10-25 23:36:48 CEST

when you played qualicups there was a working rule about db_status, not rcon status. but two days ago we realized that even after didrole tried to fix it in his new version 1.7d it still doesn't work. therefore we decided to bring old rcon status (db_info is still required).

anyway before 2h we released our news didrole published another his new update and db_status should work correctly now. but we decided to stick to rcon status because it's the same like rcon status and it's default vavle instrument that won't be broken after next update.

4 brnii 2011-10-28 13:35:53 CEST

Still, we didn't provide the server, yet we still got a warning for not producing a "rcon status" - since it is not our server, it's pretty impossible to do yet we were given a warning.