Various Suggestions
During the duration of my time playing this game, I have identified what I personally feel would be worthwhile improvements to the website and the actual game itself. To start off, I think that some aspects of reporting hackers could be improved on.
This is the web form that is currently in use. At present time, one hack report is limited to one in-game name. I have heard that you can report more by using the comments section, but I feel that in essence that would contradict the clearly stated "one ign per report." I do not know why we are limited to submitting only one, but I hypothesize that it is due to the way that the reports are automatically sorted (of course, that is if they are automatically sorted).
I think that this limitation should be removed. In response to this change, I feel that we should also be able to select multiple options when listing what hacks were used. Instead of a drop down menu, this could possibly be changed to a set of radio buttons. The number of buttons per type of hack would coincide with the number of alleged hackers being reported. Speaking of the selection of what hack type was used, I believe that the current list can be expanded upon by adding the fly hack and the long knife to the available set of options. I understand that it is possible to select "other" and then specify in the comments, but I still think that this is a worthwhile improvement to make.
Furthermore, I think that the requirement for submitting what round the hacking occurred should be dropped and added on for the actual time when the alleged hacking supposedly happened. My reasoning behind this is that not every mode (TD/ESC) utilizes the round system of play. It is easy to just put 0 and move on without specifying when the hacking occurred. Not to mention that it isn't as precise as giving the exact time in the replay. This could very well decrease the amount of false reports being sent in and decrease the amount of time the support team needs to scavenge around looking for when the hacking could have occurred.
Below, I have provided a visual interpretation of how this could look like. This also includes some other improvements such as clarification of word choice (through rewording and adding new information).
Moreover, I believe that the addition of word verification (Captcha) would also limit the amount of false reports. This, of course, could become irritating to those who submit legitimate reports, but it would be a necessary evil. Reducing the amount of false hack reports should be of utmost importance to increase the speed in which the support team responds to the hacking situation.
Furthermore, I feel that when a hack report has been submitted the automatically generated message should be changed to include Z8's official response to the hacking situation in-game. This would be a (grammatically correct) version of what GM Saidin stated in the forums. The reasoning for this would be that not everyone reads the forums and this would allow Z8 to spread their message.
Continuing on, I think there should be an option to group hacking reports if one is reporting the same alleged hacker at a different time with a different replay. By doing this, one would be able to inform the support team that this can be regarded as simply additional evidence on an already reported player.
Moving on to the actual game itself, I would love for an automatic option of sorting replays. This, when clicked, would list the replays starting from the most recent or from the oldest. It would save time for those who have amassed a great deal of replays.
In addition, I think that the wording of the message seen upon being kicked from a room should be improved to inform that there actually is a penalty. I mean, by not being able to join that room again, you are being penalized.
Also, I think that this same message should have an option to save the replay. I understand that it is possible, but not everyone knows that it is. Personally, I only recently became aware, via statements made on the forums.
On a different note, I feel that the announcement of gun winners should be disabled when in the tutorial (and perhaps have an option for it to be completely disabled). It gets in the way of text that informs you what you need to do. I understand that this is an extremely minor complaint that only affects new players, but it still is a valid one.
This is the web form that is currently in use. At present time, one hack report is limited to one in-game name. I have heard that you can report more by using the comments section, but I feel that in essence that would contradict the clearly stated "one ign per report." I do not know why we are limited to submitting only one, but I hypothesize that it is due to the way that the reports are automatically sorted (of course, that is if they are automatically sorted).
I think that this limitation should be removed. In response to this change, I feel that we should also be able to select multiple options when listing what hacks were used. Instead of a drop down menu, this could possibly be changed to a set of radio buttons. The number of buttons per type of hack would coincide with the number of alleged hackers being reported. Speaking of the selection of what hack type was used, I believe that the current list can be expanded upon by adding the fly hack and the long knife to the available set of options. I understand that it is possible to select "other" and then specify in the comments, but I still think that this is a worthwhile improvement to make.
Furthermore, I think that the requirement for submitting what round the hacking occurred should be dropped and added on for the actual time when the alleged hacking supposedly happened. My reasoning behind this is that not every mode (TD/ESC) utilizes the round system of play. It is easy to just put 0 and move on without specifying when the hacking occurred. Not to mention that it isn't as precise as giving the exact time in the replay. This could very well decrease the amount of false reports being sent in and decrease the amount of time the support team needs to scavenge around looking for when the hacking could have occurred.
Below, I have provided a visual interpretation of how this could look like. This also includes some other improvements such as clarification of word choice (through rewording and adding new information).
Moreover, I believe that the addition of word verification (Captcha) would also limit the amount of false reports. This, of course, could become irritating to those who submit legitimate reports, but it would be a necessary evil. Reducing the amount of false hack reports should be of utmost importance to increase the speed in which the support team responds to the hacking situation.
Furthermore, I feel that when a hack report has been submitted the automatically generated message should be changed to include Z8's official response to the hacking situation in-game. This would be a (grammatically correct) version of what GM Saidin stated in the forums. The reasoning for this would be that not everyone reads the forums and this would allow Z8 to spread their message.
Continuing on, I think there should be an option to group hacking reports if one is reporting the same alleged hacker at a different time with a different replay. By doing this, one would be able to inform the support team that this can be regarded as simply additional evidence on an already reported player.
Moving on to the actual game itself, I would love for an automatic option of sorting replays. This, when clicked, would list the replays starting from the most recent or from the oldest. It would save time for those who have amassed a great deal of replays.
In addition, I think that the wording of the message seen upon being kicked from a room should be improved to inform that there actually is a penalty. I mean, by not being able to join that room again, you are being penalized.
Also, I think that this same message should have an option to save the replay. I understand that it is possible, but not everyone knows that it is. Personally, I only recently became aware, via statements made on the forums.
On a different note, I feel that the announcement of gun winners should be disabled when in the tutorial (and perhaps have an option for it to be completely disabled). It gets in the way of text that informs you what you need to do. I understand that this is an extremely minor complaint that only affects new players, but it still is a valid one.
Comments
-
DrearyClouds wrote: »Which ones do you disagree with?
Grouping tickets wouldn't really be necessary. If you report someone, say player A, and another person reports player A as well, then it's more evidence that player A is likely cheating and he'll be banned.
There's no really a need for the removal of permanent weapon winner(s) notifications while someone is in the tutorial map. It probably can give new players some idea of the guns in the game and maybe go explore what the black market is if they don't already know it. -
'A wrote:Teardrop;3387657']Grouping tickets wouldn't really be necessary. If you report someone, say player A, and another person reports player A as well, then it's more evidence that player A is likely cheating and he'll be banned.
There's no really a need for the removal of permanent weapon winner(s) notifications while someone is in the tutorial map. It probably can give new players some idea of the guns in the game and maybe go explore what the black market is if they don't already know it.
I'm not quite sure we both have the same idea of what grouping tickets would look like. What I had in mind, was that the grouping process would only affect tickets from each person individually. For example, I initially report player A and this particular report will be classified as primary evidence of alleged hacking. Then, if I report player A at a different point in time with a different replay, that report will be classified as additional evidence secondary to the primary evidence in the initial report. This secondary evidence would be grouped with the primary evidence and would be given a low priority status (which would mean that the support team would only look at it if they needed more evidence to analyze).
From what I understand, your vision resembles a grouping process that is not limited within each person individually but would encompass all tickets being sent in. In that case, the first report on player A (regardless of whole sent it) would be regarded as the primary evidence and everything else would be classified as secondary evidence with a low priority status.Grouping and the kick message are meh for me, but everything else is definitely valid and should be considered.
+1 for the most part.[MOD]Nonnen wrote: »That's what I call constructive critism!
Good job.
Will be suggesting some of these.
Thank you for passing these on. -
i like the new kick messageBah if they actually looked at them it would be worth it, but the game relies heavily or entirely on auto ban, thus wasting your time.
That is a false statement. They do look at reports, but the rate at which they process them is slow. Given that there is some sort of rate, regardless of its speed, your statement of "thus wasting your time" is void and unproductive in the discussion. -
TehDWarrior wrote: »+1
Awesome suggestions would love that report more then one ign per report. (Had to report 3 people on the same replay a few days ago, with this it would've been so much faster :l) I had to do the same yesterday. Hopefully Z8 will listen. -
There should be in each game a time clock with the time how long the game is in play. Should be easier for the support to find the hacker(s).
Also they should add a time clock in the lobbyroom of the game so you know you don't have to join for like just 2 min of play. -
I'm pretty sure I agree'd with each one, and some I never noticed. VERY well made post, thanks for being apart of the community!Beefjercky wrote: »Genius. +1KoreanDeath wrote: »hehe long but i like itt good job ^.^
Thank you! I appreciate the kind words. -
Assclown321 wrote: »All reasonable and fundamental suggestions.
+ 1
Might take them a few years to get on it though. Z8 is quick to identify problems, as you can see from Crossfire's perfect in-game censoring system.
I think the underlying problem is with the developers and not Z8. If they do consider any of the in-game suggestions, it is passed on to the developers who have the final say. They could create the specific content themselves, but that would require extensive testing to make sure that it doesn't conflict with the present/future coding that the developers have created. -
This... the devs in Korea decide everything that's going to be added into this version of CrossFire.DrearyClouds wrote: »I think the underlying problem is with the developers and not Z8. If they do consider any of the in-game suggestions, it is passed on to the developers who have the final say. They could create the specific content themselves, but that would require extensive testing to make sure that it doesn't conflict with the present/future coding that the developers have created. -
Categories
- All Categories
- Z8Games
- 1 Z8 Forum Discussion & Suggestions
- 15 Z8Games Announcements
- Rules & Conduct
- 2.5K CrossFire
- 715 CrossFire Announcements
- 714 Previous Announcements
- 2 Previous Patch Notes
- 322 Community
- 12 Modes
- 393 Suggestions
- 16 Clan Discussion and Recruitment
- 73 CF Competitive Forum
- 1 CFCL
- 16 Looking for a Team?
- 524 CrossFire Support
- 7 Suggestion
- 15 CrossFire Guides
- 37 CrossFire Off Topic