Crypt 2017

[JustJoshuaVega]

Your statement of Junz isn’t justified at all because he wasn’t the one who closed it, also if it was really rigged for mk then how did BBZ slip in a final run lol?

Bingo


Sent from my iPhone using Tapatalk

[imaginary]

Your statement of Junz isn’t justified at all because he wasn’t the one who closed it, also if it was really rigged for mk then how did BBZ slip in a final run lol?

Didn’t say Junz rigged it and BBZ did their run on Wednesday. Also it’s all staff members’ fault who are in charge of crypt. They should have chosen a specific time not only the date

- - - Updated - - -

Wednesday or Tuesday

[JustJoshuaVega]

No they did a run yesterday and they completely failed.


Sent from my iPhone using Tapatalk

[MrOmz]

Didn’t say Junz rigged it and BBZ did their run on Wednesday. Also it’s all staff members’ fault who are in charge of crypt. They should have chosen a specific time not only the date

- - - Updated - - -

Wednesday or Tuesday

Bbz did do a run yesterday.

[imaginary]

No they did a run yesterday and they completely failed.


Sent from my iPhone using Tapatalk

Bbz did do a run yesterday.

Uh yea? They did an early run and failed what does that have to do with this situation

- - - Updated - - -

Their winning run was on Wednesday or Tuesday

[LAZULI]

Really??


Sent from my iPhone using Tapatalk

[Junz]

If you have any issues about the time crypt was closed then submit a ticket about it.
No need to start arguments about it on this thread.
Closing time was approximate, and it clearly changed due to a very specific circumstance, that wasn't accounted for. It's as simple as that.
If you want to blame someone, blame whoever decided it'd be a good idea to abuse exploits in crypt.
That's not the fault of any crypt organiser, and it can't magically be patched in a day or two. It'd take a lengthy period of time to fix the exploit.
So crypt won't be re-opened, the decision was clearly already made.

[JustJoshuaVega]

If you have any issues about the time crypt was closed then submit a ticket about it.
No need to start arguments about it on this thread.
Closing time was approximate, and it clearly changed due to a very specific circumstance, that wasn't accounted for. It's as simple as that.
If you want to blame someone, blame whoever decided it'd be a good idea to abuse exploits in crypt.
That's not the fault of any crypt organiser, and it can't magically be patched in a day or two. It'd take a lengthy period of time to fix the exploit.
So crypt won't be re-opened, the decision was clearly already made.

True


Sent from my iPhone using Tapatalk

[N!chola$]

Congrats to the winners!
I know I'm late ;p

[JeffV]

It wasn't a glitch, The leader of Patch was hacking, running fast over walls and shooting explosives with his gold desert eagle very fast. You guys will call that a glitch? That's why they were disqualified from crypt.