[Hackers] suggestions/complaints/criticisms
Comments
-
Another thing to note is that players do not know any numbers from XTrap. What they're stating is assumptions that XTrap is not doing any work. 47.5623% of the numbers on the internet are made up from assumptions.
XTrap does not give any numbers out to the general population of players, so what you see is what does get through. What doesn't get through is never shown.
By the way, the room crashing hack isn't even a hack. It's a glitch in the game's coding, which is being fixed. -
Another thing to note is that players do not know any numbers from XTrap. What they're stating is assumptions that XTrap is not doing any work. 47.5623% of the numbers on the internet are made up from assumptions.
XTrap does not give any numbers out to the general population of players, so what you see is what does get through. What doesn't get through is never shown.
By the way, the room crashing hack isn't even a hack. It's a glitch in the game's coding, which is being fixed.
Kinda like when you fall into the well in Mine SnD and everyone gets DC-ed from the room -
[GM]Saidin wrote: »It should be noted that getting the name correct (where possible) is one of the best things you can do when reporting a hacker.
Nice point, but do you really want us to go through all the steps?
Can we have a button called "create report" in replay to record the players name in first person view?
Will the review staff feel happy when the input name are accurate?
In current forum font, can you tell me "Hl0" is "HL0", "HLO", "Hi0" or "HiO".
These are human factors that can be removed. And once it is removed, it will make things easier, at least a database can be build from reports and algorithm can be created to provide minimal number of file to be reviewed. -
Can we have a button called "create report" in replay to record the players name in first person view?
I don't see why this hasn't already been implemented - its an obvious and effective method of ensuring that all reports are useable and that the maximum amount of hackers are reported. A large number of reports would come in, but if that is seriously an issue here then people really aren't putting much thought into this whole process... -
GodsGunman wrote: »Still going to work on this, anyone have more topics?
I think the topic you have listed in the original post will not cause anyone's attention. Everyone knows z8 is doing their best to control the hackers, and they would not sell hacking code to ruin their own product. All the problem come from the FACT there are too many hackers now and then. It is mainly a rage about the efficiency of the fix. When combined with the some forum policy, report response policy and the delay of the response, people starts to get ****ed.
This will go through, once z8's promise about "new anti-hack" starts to work.
I think a better topic should be the prefixing, tuning before start to game, mouse acceleration for example, after I disabled the mouse precision in windows 7 all based on memory and guess, then I learned I still have not totally fixed it yet, that is really an upset. So a guide of all these tiny but useful information bundled together will be a good article. -
The biggest problem is the general level of acceptance most in game players have for hackers.
If the majority of players simply kicked hackers on sight then hacking won't be so common.
Because hackers are allowed to hack from the players it has grown to these levels. -
I don't see why this hasn't already been implemented - its an obvious and effective method of ensuring that all reports are useable and that the maximum amount of hackers are reported. A large number of reports would come in, but if that is seriously an issue here then people really aren't putting much thought into this whole process...
Right what I have been thinking. In the webform, we have to input hacker name, round, ....... If these information can not be abstracted from replay, then how could a reporter to put it correctly. If the information are already in the replay, a button would save lots of effort from both reporter and reviewer side. The time slot can be recorded with the name of the hacker, and a report just need a generated file with the replay. Reviewer can screen the reports but an scan program to make sure the hacker is not already reported, or the same game replay have already been review at the same time slot. And reviewer might jump directly to the reported time slot to watch the reported player. Would this help to increase the processing speed.
Categories
- All Categories
- Z8Games
- Off-Topic - Go To Game OT Forums
- 1 Z8 Forum Discussion & Suggestions
- 16 Z8Games Announcements
- Rules & Conduct
- 5.4K CrossFire
- 1K CrossFire Announcements
- 1K Previous Announcements
- 2 Previous Patch Notes
- 1.4K Community
- 122 Modes
- 620 Suggestions
- 86 Clan Discussion and Recruitment
- 276 CF Competitive Forum
- 19 CFCL
- 26 Looking for a Team?
- 740 CrossFire Support
- 61 Suggestion
- 124 Bugs
- 29 CrossFire Guides
- 174 Technical Issues
- 47 CrossFire Off Topic
