MOTG Suggestions for next year.
in Ghost Mode
So a lot of players are pretty mad about how MOTG happend this year, to some people it was very unfair, so I think these suggestions might help for next years MOTG.
A problem I saw that happen this year that a lot of teams were getting dqed for was for the two year being hack free. This was really causing a lot of teams to getting dqed, I understand that the GM's are just trying to be on the safe side but I don't think that really helps cause we are suppose to be recording so I mean you can see if someone is hacking or not, and another thing is that the whole team has to suffer and you guys wait til the last minute to tell us, so maybe if you guys could've told us ahead of time so we can get some time to change the teams that would help A LOT.
Another problem I saw teams were so confused why they were getting dqed and they would ask the gms "why" then when you guys replied to us you would say "it is not up for debate" if you guys could take the time to listen to our opinions it would really make a difference
A suggestion I would like to give, if a team gets dqed for a hacker being on there team or something, I believe that the whole team shouldn't be punished for that maybe you guys can just punish that one individual player who messed it up for the whole team, and what you can do with the rest of the team is give them a certain amount of time to find another time and if they don't find a team within that period then they can get dqed.
Other than that, that's all I really had to say, hopefully the gm's will take some time to look at this
Also if any of you guys have another suggestion you want to add-on to this you can.
A problem I saw that happen this year that a lot of teams were getting dqed for was for the two year being hack free. This was really causing a lot of teams to getting dqed, I understand that the GM's are just trying to be on the safe side but I don't think that really helps cause we are suppose to be recording so I mean you can see if someone is hacking or not, and another thing is that the whole team has to suffer and you guys wait til the last minute to tell us, so maybe if you guys could've told us ahead of time so we can get some time to change the teams that would help A LOT.
Another problem I saw teams were so confused why they were getting dqed and they would ask the gms "why" then when you guys replied to us you would say "it is not up for debate" if you guys could take the time to listen to our opinions it would really make a difference
A suggestion I would like to give, if a team gets dqed for a hacker being on there team or something, I believe that the whole team shouldn't be punished for that maybe you guys can just punish that one individual player who messed it up for the whole team, and what you can do with the rest of the team is give them a certain amount of time to find another time and if they don't find a team within that period then they can get dqed.
Other than that, that's all I really had to say, hopefully the gm's will take some time to look at this
Also if any of you guys have another suggestion you want to add-on to this you can.
Comments
-
So a lot of players are pretty mad about how MOTG happend this year, to some people it was very unfair, so I think these suggestions might help for next years MOTG.
A problem I saw that happen this year that a lot of teams were getting dqed for was for the two year being hack free. This was really causing a lot of teams to getting dqed, I understand that the GM's are just trying to be on the safe side but I don't think that really helps cause we are suppose to be recording so I mean you can see if someone is hacking or not, and another thing is that the whole team has to suffer and you guys wait til the last minute to tell us, so maybe if you guys could've told us ahead of time so we can get some time to change the teams that would help A LOT.
Another problem I saw teams were so confused why they were getting dqed and they would ask the gms "why" then when you guys replied to us you would say "it is not up for debate" if you guys could take the time to listen to our opinions it would really make a difference
A suggestion I would like to give, if a team gets dqed for a hacker being on there team or something, I believe that the whole team shouldn't be punished for that maybe you guys can just punish that one individual player who messed it up for the whole team, and what you can do with the rest of the team is give them a certain amount of time to find another time and if they don't find a team within that period then they can get dqed.
Other than that, that's all I really had to say, hopefully the gm's will take some time to look at this
Also if any of you guys have another suggestion you want to add-on to this you can.
The two year hack free requirement is less about being safe or making sure you're legit now, but you simply don't deserve to participate in an event and possibly win a reward if you used to hack during the past. -
Well one GM did reply to one player who bothered to ask in a humane manner since he didn't have caps on and wasn't swearing after every other word to why his team got dqed and Kanadian gave him two reasons why a team could of gotten dqed, so the "it is not up for debate" is false instead you've most likely gotten ignored.
-
So a lot of players are pretty mad about how MOTG happend this year, to some people it was very unfair, so I think these suggestions might help for next years MOTG.
A problem I saw that happen this year that a lot of teams were getting dqed for was for the two year being hack free. This was really causing a lot of teams to getting dqed, I understand that the GM's are just trying to be on the safe side but I don't think that really helps cause we are suppose to be recording so I mean you can see if someone is hacking or not, and another thing is that the whole team has to suffer and you guys wait til the last minute to tell us, so maybe if you guys could've told us ahead of time so we can get some time to change the teams that would help A LOT.
Another problem I saw teams were so confused why they were getting dqed and they would ask the gms "why" then when you guys replied to us you would say "it is not up for debate" if you guys could take the time to listen to our opinions it would really make a difference
A suggestion I would like to give, if a team gets dqed for a hacker being on there team or something, I believe that the whole team shouldn't be punished for that maybe you guys can just punish that one individual player who messed it up for the whole team, and what you can do with the rest of the team is give them a certain amount of time to find another time and if they don't find a team within that period then they can get dqed.
Other than that, that's all I really had to say, hopefully the gm's will take some time to look at this
Also if any of you guys have another suggestion you want to add-on to this you can.
The following is my opinion of your points as someone who did not participate but thought about joining a team and who has been watching this unfold to a degree. My input on OP is in red....the green is what i'd tack on as what i noticed and how it might be better done in the future.
-The 2 year Hack Free thing...as Danah stated...is more of a punishment for having hacked before rather than them being afraid one will hack now. However, I remember seeing this aspect of 2 year hack free being stated on the announcement post from day 1. So you can't use the excuse of 'we didn't know until last minute' on that, one. If it was up to me, anyone without an honorable ribbon wouldnt be able to participate anyways and is probably how it should be viewed by the 'Team leader' who's making the team to ensure they're team is legit.
-What's not up for debate is getting your team re-instated regardless of the why. The reason the why didn't get addressed for most people is because the asking part was done rudely a manner as possible. I get it....you're mad and frustrated. But things don't get better with rudeness especially with an occasional disregard for forum rules in those posts...in fact they generally get worse.
-While I partially agree with IF someone on a team is found to be DQed by the GMs that the entire rest of the team shouldn't be punished (despite the fact that wouldn't happen if the person who put the team together held people to higher standards like knowing the others fairly well and making sure they have HSR etc etc) in the case of this year the time constraints on the organization of the tourny was very restricting and to give the team 'a certain amount of time' could have delayed thing even more.
+The biggest issue I observed were that teams had partial information when it came to the date and time at the beginning when the event was announced and open for team registration. The best they had to offer at that point was "one of these two weekends at the end of March". And IIRC it wasn't until 5 days before registration ended that they eliminated it down to just one possible weekend. and the actual date still wasn't decided until close to the end of registration. Not to mention no real idea of an expected/pending time table was given so potential players couldn't even really figure out if they'd in fact be available to participate and thus couldn't really commit to a team especially since if they committed to a team and the team was put into the tournament roster and then the team fails to show up fully that they all get banned from future tournies.
My suggestion to that is to take this years and/or last years time table for the event and use it to get a general idea for times and how long it'll take but mostly to decide on an exact day the tourny will be held before even announcing it. Add in a *depending on amount of teams times may change. underneath of the tentative schedule and it'd be MUCH better than the way it went this time. Even better if they start the whole process in mid February with a verification of teams in early march and a final roster posted a week before the tourny actually hits....not 2 days before.
That alone should make things a lot better and ease the headache that the time crunch on all of this caused. -
The following is my opinion of your points as someone who did not participate but thought about joining a team and who has been watching this unfold to a degree. My input on OP is in red....the green is what i'd tack on as what i noticed and how it might be better done in the future.
-The 2 year Hack Free thing...as Danah stated...is more of a punishment for having hacked before rather than them being afraid one will hack now. However, I remember seeing this aspect of 2 year hack free being stated on the announcement post from day 1. So you can't use the excuse of 'we didn't know until last minute' on that, one. If it was up to me, anyone without an honorable ribbon wouldnt be able to participate anyways and is probably how it should be viewed by the 'Team leader' who's making the team to ensure they're team is legit.
-What's not up for debate is getting your team re-instated regardless of the why. The reason the why didn't get addressed for most people is because the asking part was done rudely a manner as possible. I get it....you're mad and frustrated. But things don't get better with rudeness especially with an occasional disregard for forum rules in those posts...in fact they generally get worse.
-While I partially agree with IF someone on a team is found to be DQed by the GMs that the entire rest of the team shouldn't be punished (despite the fact that wouldn't happen if the person who put the team together held people to higher standards like knowing the others fairly well and making sure they have HSR etc etc) in the case of this year the time constraints on the organization of the tourny was very restricting and to give the team 'a certain amount of time' could have delayed thing even more.
+The biggest issue I observed were that teams had partial information when it came to the date and time at the beginning when the event was announced and open for team registration. The best they had to offer at that point was "one of these two weekends at the end of March". And IIRC it wasn't until 5 days before registration ended that they eliminated it down to just one possible weekend. and the actual date still wasn't decided until close to the end of registration. Not to mention no real idea of an expected/pending time table was given so potential players couldn't even really figure out if they'd in fact be available to participate and thus couldn't really commit to a team especially since if they committed to a team and the team was put into the tournament roster and then the team fails to show up fully that they all get banned from future tournies.
My suggestion to that is to take this years and/or last years time table for the event and use it to get a general idea for times and how long it'll take but mostly to decide on an exact day the tourny will be held before even announcing it. Add in a *depending on amount of teams times may change. underneath of the tentative schedule and it'd be MUCH better than the way it went this time. Even better if they start the whole process in mid February with a verification of teams in early march and a final roster posted a week before the tourny actually hits....not 2 days before.
That alone should make things a lot better and ease the headache that the time crunch on all of this caused.
This pretty much hits the nail on the head. The biggest issue with MOTG has ALWAYS been lack of sufficient information in a timely manner. I'd really love to see a tournament where all the dates, times, and rules are posted right at the beginning with no changes made. You can even post a poll earlier and see what dates are best for the players if you feel the need to. We're all more than happy to try and help the tournament run as smoothly as possible.
The things I thought you guys did really well this time was that you stuck to the time-table very well (after if was finally posted) so players knew exactly when they were supposed to be play. Triton on the forums answering questions and updating the bracket was A+ in my opinion. Having both Jessy and Cinder in game and using the announcement feature was also well done. If the servers hadn't been acting up I think we could all agree that the actual "play date" of the tournament would be very well executed.
Side note: Some people have been talking about the DQs for the honorable soldier ribbon and personally I think this is a non-issue. This is coming from a person who had his team DQed last year as well. As someone organizing a team I just wouldn't take a chance playing anyone without an HSR and if you are going to i'd have said person send a ticket in and SS the response that they ARE allowed to play. This way there can be no miscommunication, no surprises, and if you get DQed later on you have solid evidence of your players legitimacy. -
I disagree that only the player should be punished and the whole team shouldn't. If they let the team stay in the tournament, the player that got banned will just swap out the account with another one and play anyway, making the rule useless. Besides, it's not a hard rule to follow, if your acc has a HSR, you're good, if you don't, think about when you last got banned. If you don't remember if it's been 2 years, send a ticket.
My acc was banned for insulting and trolling recently and I didn't know if that would count so I sent a ticket just to make sure
but yeah the thing I liked most about the tourney was how it only lasted 1 day and followed the schedule perfectly, meaning I only had to clear 1 day for the tourney as opposed to making sure I don't have plans for a whole weekend or 2 consecutive weekends.
one suggestion is to plan some of the main tournament info before releasing it to the public i.e. start time, date, rules, etc. so that you're already prepared and people don't have to wait till the last day for information.
another suggestion but prob not that important is the 1st place prize. I would've liked some ZP on top of the perm weapon even something small like 10k :^)
but overall this was probably one of the most fun tournaments I've ever played in and ive played in every single one since 2013.
Categories
- All Categories
- Z8Games
- 1 Z8 Forum Discussion & Suggestions
- 15 Z8Games Announcements
- Rules & Conduct
- 2.5K CrossFire
- 732 CrossFire Announcements
- 724 Previous Announcements
- 2 Previous Patch Notes
- 331 Community
- 12 Modes
- 396 Suggestions
- 16 Clan Discussion and Recruitment
- 81 CF Competitive Forum
- 1 CFCL
- 16 Looking for a Team?
- 527 CrossFire Support
- 8 Suggestion
- 15 CrossFire Guides
- 38 CrossFire Off Topic