Rematch Button

[SirSebstar]

no function that allows you to create br's on your own would not consitute not a bug.or in clearer english
it was tested that the functionality would not screw up the cc database. The unexpected functionality of making br's is a bug.
this is a bug, the fact that you can make it do something that was OBVIOUSLY not intended is not a functionality. please use a bit of common sense.

[patrickaa317]

no function that allows you to create br's on your own would not consitute not a bug.or in clearer english
it was tested that the functionality would not screw up the cc database. The unexpected functionality of making br's is a bug.
this is a bug, the fact that you can make it do something that was OBVIOUSLY not intended is not a functionality. please use a bit of common sense.

Can we get a link to the announcement where the intended purpose of this functionality is??? With any development project now days, I would assume all requirements are clearly defined, coded to, and tested against. Perhaps a member can be added to the Beta testers that types up the new func details and they are announced to the public prior to go-live instead of getting these surprises.

IMO, exploiting all the bugs is the best way to get these development cycles. Another member should be added to the Beta testers to test out the user experience of said features.

It's 2013, development cycles (requirements > dev > unit > functional > user testing > go-live) is not a new concept anymore.

Not trying to be a jerk, just trying to fix this from happening with every [unexpected] release. At least tell us "We are going live Saturday with a new blah blah blah feature". So we aren't surprised saturday when everything is different when we log in, we can get used to the upcoming concepts before having them thrown at us. Just my two cents.

[SirSebstar]

i totally agree tht its nice to see a new function added, and its a shame we were not appriced beforehand and such a big bug was still present. but lets face it, its an exploit bigger then what glg got banned over.

[IcePack]

useing a bug, even a blatant one like this is against the site ruels.
Either drop it yourself, or expect the games to be deleted without prior information. creating br's is fun if you are the first to find out about it, but this will hopefully be fixed asap. the developers have been notified

what part of this is not a bug do you not fucking understand.

we now have beta testers. this was tested. CC implemented it.

this is how CC wants it.

As has been mentioned elsewhere, thats not the case. There's an official announcement on it here if you'd like to read further.

icepack

[greenoaks]

useing a bug, even a blatant one like this is against the site ruels.
Either drop it yourself, or expect the games to be deleted without prior information. creating br's is fun if you are the first to find out about it, but this will hopefully be fixed asap. the developers have been notified

what part of this is not a bug do you not fucking understand.

we now have beta testers. this was tested. CC implemented it.

this is how CC wants it.

As has been mentioned elsewhere, thats not the case. There's an official announcement on it here if you'd like to read further.

icepack

that announcement didn't exist at the time so why should we assume an awesome feature is a bug.

[patrickaa317]

i totally agree tht its nice to see a new function added, and its a shame we were not appriced beforehand and such a big bug was still present. but lets face it, its an exploit bigger then what glg got banned over.

Until announcement was out, how are we supposed to know what is a bug and what is not? If it is that big of a bug or exploitation, where is backout plan on new code developed? If it is that big of bug, back out the code, get it right, THEN put it back in...

If they put a button in the middle of the screen that isn't meant to be clicked, is it our fault for clicking it or theirs for even putting it there?

[Jdsizzleslice]

i totally agree tht its nice to see a new function added, and its a shame we were not appriced beforehand and such a big bug was still present. but lets face it, its an exploit bigger then what glg got banned over.

Until announcement was out, how are we supposed to know what is a bug and what is not? If it is that big of a bug or exploitation, where is backout plan on new code developed? If it is that big of bug, back out the code, get it right, THEN put it back in...

If they put a button in the middle of the screen that isn't meant to be clicked, is it our fault for clicking it or theirs for even putting it there?

That is why no one is being punished.

[pickleofdoom]

Very strange that the button just appears there and no announcement beforehand. eminded me a bit of that April fools day "flip the board" button.

I guess i had better drop that battle royale game i got invited to. Saw a battle royale speed game up yesterday. Goodness knows how that one got created.

[SirSebstar]

There is not much you can do, it things just don't go as you really want too. the announcement was planned.

..........., and an announcement was going to be here earlier (barring that my computer didn't bonk out the night of the update!), but alas, here we are. ..........

BMO

quote="pickleofdoom"]Very strange that the button just appears there and no announcement beforehand. eminded me a bit of that April fools day "flip the board" button.

I guess i had better drop that battle royale game i got invited to. Saw a battle royale speed game up yesterday. Goodness knows how that one got created.[/quote]