Multiple IGNs per Hack Report
in Suggestions
Don't get me wrong. I appreciate the recent update to the replay system. I'm really glad that I don't have to sit through a whole match just to save a replay. However, uploading replays is still a very tedious process. Especially when one has to upload the same replay 3, 4, 5... times for several different hackers. Not too mention the staff who review the hack reports have to waste their time rewatching replays just to ban hackers #2, 3, 4, 5.....and so on.
I suggest a new layout for the hack report system where a player can report several players with one replay--ONE upload
It would be something like this:
______________________________________
In Game Name of Hacker #1(IGN):________
Hacking Type:_________________________
Rounds that Hacking Occurred : __________
Time when Hacking Occurred : ___________
In Game Name of Hacker #2(IGN):________
Hacking Type:_________________________
Rounds that Hacking Occurred : __________
Time when Hacking Occurred : ___________
In Game Name of Hacker #3(IGN):________
Hacking Type:_________________________
Rounds that Hacking Occurred : __________
Time when Hacking Occurred : ___________
In Game Name of Hacker #4(IGN):________
Hacking Type:_________________________
Rounds that Hacking Occurred : __________
Time when Hacking Occurred : ___________
Comments:
Replay File (*.cfr file) of Hacker:* (Max. file size = 32MB) "CHOOSE FILE"
______________________________________
Now, if there is only one hacker to report you leave the other slots blank, obviously. BUT, if you need to report many hackers, you can do so and not have to spend the rest of your day uploading replays. And we might actually be able to go back to playing the game which is what we wanted to do in the first place.
Suggestions, ideas, flames?
I suggest a new layout for the hack report system where a player can report several players with one replay--ONE upload
It would be something like this:
______________________________________
In Game Name of Hacker #1(IGN):________
Hacking Type:_________________________
Rounds that Hacking Occurred : __________
Time when Hacking Occurred : ___________
In Game Name of Hacker #2(IGN):________
Hacking Type:_________________________
Rounds that Hacking Occurred : __________
Time when Hacking Occurred : ___________
In Game Name of Hacker #3(IGN):________
Hacking Type:_________________________
Rounds that Hacking Occurred : __________
Time when Hacking Occurred : ___________
In Game Name of Hacker #4(IGN):________
Hacking Type:_________________________
Rounds that Hacking Occurred : __________
Time when Hacking Occurred : ___________
Comments:
Replay File (*.cfr file) of Hacker:* (Max. file size = 32MB) "CHOOSE FILE"
______________________________________
Now, if there is only one hacker to report you leave the other slots blank, obviously. BUT, if you need to report many hackers, you can do so and not have to spend the rest of your day uploading replays. And we might actually be able to go back to playing the game which is what we wanted to do in the first place.
Suggestions, ideas, flames?
Comments
-
When the format first came out for support tickets, I would put in the secondary or more in game names that were hacking onto one report in the comments section. But that was then... now I do one name per ticket submitted.
Then I realized that this is really not about the replay that we submit, but the in game name CONNECTED to the replay.
What I'm trying to say is that for a good organizational purpose and streamlining efficiency, needs to be receiving 1 reported name per replay.
It's like creating a dossier on that reported in game name.
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
- 323 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