Denial HCs Round 27
Do As I Say Not As I Do!!!!
|
Re: Denial HCs Round 27
How can anyone decide to exploit a coding loophole instead of reporting it. Im disgusted, so should the Denial members be.
|
Re: Denial HCs Round 27
"Cheating Denied" :salute:
|
Re: Denial HCs Round 27
Quote:
|
Re: Denial HCs Round 27
Amusingly if they dont see this as cheating i find it amusing. I hope of course they are not been re-oppend/given a second chance. If you exploit somthing without reporting it its cheating. plain and simple. And if your caught you need to be punished. Dont know of course all the details, all im hearing is rumours and gossip so far. But, if this is true that the HC of Denial have infact abused a loophole and exploited it for their own needs and then that is cheating and should remain closed. End off tbh.
|
Re: Denial HCs Round 27
Or reset... but thats happening allready
|
Re: Denial HCs Round 27
multihunters need to show some balls and delete them they cheated end of
|
Re: Denial HCs Round 27
Quote:
|
Re: Denial HCs Round 27
WIN for denial! smart move!
|
Re: Denial HCs Round 27
I just laughed reading this thread. So. What bug have they abused? As im not on irc i dont know anthing other then what is posted here. Who is closed? lets name and shame them :p
But i do agree if they have been closed then they should remain closed. |
Re: Denial HCs Round 27
If they have exploited something ( which is clearly for their own gain ) they should be closed and left closed.
|
Re: Denial HCs Round 27
Couldn't happen to a nicer bunch of players.
|
Re: Denial HCs Round 27
i too scared to name and shame or comment on whats happen incase i get something wrong and look like an idiot..
all i am willing to say is Denial HCs been bad, very bad,, bug abusers!!!! but apparantly they not even bug abusing like little bugs they actually hackz0red the game in some way or another :| html coding blah blah? some ugly woman with some merry men the ones who got closed tho *apparantly* this what i hear but Denial bug abuse > Ascendancy bug abuse? |
Re: Denial HCs Round 27
Quote:
|
Re: Denial HCs Round 27
So what exactly did they do?
|
Re: Denial HCs Round 27
reese eskero koks and venox are denial hc so was it just some of them or all of them
when will the denial trolling squad show up to fight there cause |
Re: Denial HCs Round 27
venox is still open, so not him. they used greasemonkey to edit their factory counts in orders to zero.
|
Re: Denial HCs Round 27
Utter rank incompetance in the coder
There is no excuse whatsoever for this bug |
Re: Denial HCs Round 27
All Denial associates have been banned from talking on AD
|
Re: Denial HCs Round 27
Quote:
Quote:
|
Re: Denial HCs Round 27
Quote:
Hint to whoever coded it. When you recieve a post form for production orders ( or indeed anything ), you dont trust anything that is submitted. You find out *yourself* from the database for anything that is needed, such as number of factories that the person has. You check *yourself* from the database that there are enough resources to build the requested ships You check *yourself* to see if there are enough production slots You never ever ever accept verbitem anything that is sent from the client, and absolutely never ever ever ever ever assemble an sql string directly from data submitted without doing checks on it or you open yourself up to sql injection attacks if not using prepared statements, which i doubt you are. |
Re: Denial HCs Round 27
Quote:
|
Re: Denial HCs Round 27
accessing other alliances tools accounts last round and now this, good honest people then!!
|
Re: Denial HCs Round 27
Denial members might want to consider new HCs or a new alliance...
|
Re: Denial HCs Round 27
Quote:
any suggestions? |
Re: Denial HCs Round 27
Quote:
You know we'll win anyway :p |
Re: Denial HCs Round 27
They should get punished for getting caught. Idiots! Learn your lesson! If u find an exploit, then keep it secret! If you get caught, deny, deny, deny! That is what the system forces you to do! Blame the game!!!
|
Re: Denial HCs Round 27
Quote:
Someone to pre-emptively close i suspect :) |
Re: Denial HCs Round 27
Nah, that Asc HC forced me to write that. I am just a messenger.
|
Re: Denial HCs Round 27
You spoke to all 58 HC?
That's pretty good going man. |
Re: Denial HCs Round 27
Thats a trick question.
|
Re: Denial HCs Round 27
i hope this isn't true
|
Re: Denial HCs Round 27
Accounts should stay closed rest of round.
I also suggest jail time |
Re: Denial HCs Round 27
Quote:
|
Re: Denial HCs Round 27
Quote:
They should be closed and left closed. anything more is overkill and anything less is worthless. Since it would probably cripple the alliance, tag wise if the hc accounts were deleted they might want to assign someone else to be a HC of the alliance for the time being. |
Re: Denial HCs Round 27
VenoX is right, punish the offenders only. In my opinion they should remain closed for the remainder of the round though, which doesn't seem to be the case.
@Phil: VenoX is HC and appears to be clean in all of this so the tag should not be affected in any case. |
Re: Denial HCs Round 27
Quote:
But I'd like to know if I get a present because my galmates got closed. That kinda punishes me and I didn't do anything wrong. :( |
Re: Denial HCs Round 27
Quote:
Removing the denial tag is irrelevant. |
Re: Denial HCs Round 27
Quote:
|
Re: Denial HCs Round 27
Quote:
But HC are clearly responsible, as they are responsible for their alliance and ultimately the institutional conduct of their members. Which is different to an ordinary peon, as they aren't responsible for anyone else apart from themselves. HC determine the rules of a hierarchical organisation, not members. So on that basis, all of the HC and the members directly responsible seems pretty fair. It would be the same for directors of a company. |
Re: Denial HCs Round 27
dumb question but what about the people that were affected by their cheating , eg someone landing on them with their production bug and losing their ships are they gonna be compensated
|
Re: Denial HCs Round 27
quite simply blame Kenny for this madness
|
Re: Denial HCs Round 27
I dunno, they did better when Kenny was around cutting his shit videos :|
|
Re: Denial HCs Round 27
Quote:
|
Re: Denial HCs Round 27
Quote:
|
Re: Denial HCs Round 27
Hey guys, guess who's back?
Some highlights: (@Reese) A PA SUPPORT TEAM MEMBER told us this was okay That was koks, who also happens to be Denial HC, but that clearly has nothing to do with anything. (@Reese) this was a practice that had gone basically the last 5+ rounds Haha. (@Reese) we were under the impression this was no different that setting a order to "never" had been done in the past Who would have thought that exploiting a loophole by using an external plugin to change the HTML code would be against the rules! (@Reese) im not gonna name the other members In accordance with the principle of name and shame, I am happy to tell you that one of the other people that got closed was Fuzzy (though the less informed among you might know him better under the name of el-"I never cheat"-viz). |
Re: Denial HCs Round 27
The world would be far less informed if it wasnt for you mz :hugs:
|
Re: Denial HCs Round 27
Since im such a perfect person, ill just say that they never changed any html to do this!
They changed a HTTP request to the server, either POST or GET. I havent bothered checking too much about it tbh. All in all, it lacked serverside checking and you could change it to what you wanted clientside.. I'm quite sure it could be used the other way around aswell, use more factories than you had.. Did anyone test that btw? |
Re: Denial HCs Round 27
Clicking the "back" button on your browser basically accomplishes that. You force a revert to a previous version of the page, thereby circumventing the client-side checking. Since there was no server-side checking, you could basically do whatever you like.
Note that this is a far cry from actually engineering a page or request for yourself. |
Re: Denial HCs Round 27
Quote:
|
All times are GMT +1. The time now is 07:09. |
Powered by vBulletin® Version 3.8.1
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2002 - 2018