Discovery Gaming Community
Admin Feedback Thread 2.0 - Printable Version

+- Discovery Gaming Community (https://discoverygc.com/forums)
+-- Forum: Rules & Requests (https://discoverygc.com/forums/forumdisplay.php?fid=6)
+--- Forum: Rules (https://discoverygc.com/forums/forumdisplay.php?fid=25)
+---- Forum: Faction Rules (https://discoverygc.com/forums/forumdisplay.php?fid=46)
+----- Forum: Faction Review and Feedback (https://discoverygc.com/forums/forumdisplay.php?fid=135)
+------ Forum: Archived Feedback Threads (https://discoverygc.com/forums/forumdisplay.php?fid=484)
+------ Thread: Admin Feedback Thread 2.0 (/showthread.php?tid=147306)

Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40


RE: Admin Feedback Thread 2.0 - sindroms - 09-29-2017

o7


RE: Admin Feedback Thread 2.0 - Thunderer - 10-18-2017

https://i.imgur.com/DYB9gmq.jpg?2

Thanks!

(Not my Valor btw, only noobs buy CAU 7-s)


RE: Admin Feedback Thread 2.0 - Karlotta - 10-18-2017

Although I've personally never shot at a POB weapons platform, and have never participated in any base sieges except on the defending side, I'd be interested to know where and when it has been said or signaled by the admins that disabling them was considered a rule violation. It's not listed in the exploits in the rules, as far as I could see. It was was always my impression that it was known and tolerated by the admins, in the discussions I saw.


RE: Admin Feedback Thread 2.0 - Karlotta - 10-18-2017

Er... for some reason the editing posts of posts doesnt work here. Tripple sorry.


RE: Admin Feedback Thread 2.0 - Alex. - 10-18-2017

(10-18-2017, 06:45 PM)Karlotta Wrote: Er... for some reason the editing posts of posts doesnt work here. Tripple sorry.

I think that might be tied to your probation status. Not sure if it's intentional or not.


RE: Admin Feedback Thread 2.0 - sindroms - 10-18-2017

We included part of the evidence in the post exactly for this reason - there is a difference between attacking a weapon platform to destroy it and glitching it. Essentially, when the plugin respawns a platform, it has a chance to assign the wrong defense model to its npc (the platform is basically an npc without an engine) and the exploit is described as an attempt to keep destroying the platform over and over until it glitches out. This is, as I hope people understand, not an intended mechanic for the POB plugin. This issue was documented and was to be fixed with POB 3.0, but that was delayed. Sadly, it seems as though it was more widespread than we hoped and was used to completely remove any sort of defense a player spent hours of building simply by - for the lack of a better word - cheating.

EDIT: The exploits rule 5.0 is a rule in by itself. The sub-section of the rule is a collection of game mechanics as examples. This does not by any means imply that those are the -only- exploits that are forbidden. Exploits as a THING is forbidden.


RE: Admin Feedback Thread 2.0 - Karlotta - 10-18-2017

I can see how it's considered cheating. What I found strange is not only not listed in the list of exploits, but has also been mentioned numerous times on the forum in plain sight of admins, and I've never seen anyone say that it's considered cheating. Of course its possible that it was said and I didnt see it, or maybe in PM. What I found even more disappointing was that it resulted directly in an activity-killing 6 month ban, when there were other possible ways to sanction this. Maybe that already happened, but I didn't see sanctions or warnings for that particular exploit/cheat mentioned anywhere except for the 6 month ban of Wesker.


RE: Admin Feedback Thread 2.0 - Tutashkhia - 10-18-2017

Everyone, at least the majority of the community, knew about this bug and abused it. Yes, abused it! And the only explanation I find in banning Wesker for 6 months is to give others an example of abusing this bug. But as the person above me mentioned, there could be found other possible ways to sanction this.

My point is that this was too much for this "bug-abusing", as almost everyone used this bug when it was possible.


RE: Admin Feedback Thread 2.0 - sindroms - 10-18-2017

I would like to direct you to the fact that most of the result were warnings. Wesker landed a harsh punishment because of his repeated bans which have happened over the span of the last year.


RE: Admin Feedback Thread 2.0 - sindroms - 10-18-2017

Please report these actions via the appropriate forum and they will be handled just the same.