Crossfire 3.2 Launches
•
19 Oct 2010, 15:51
•
News
Crossfire 3.2 Launches
As part of the series of incremental site upgrades which will culminate with Crossfire 4.0, Crossfire 3.2 has been launched. Those of you who saw my sneak preview journal yesterday evening will be aware of what is new, but to those of you who did not, here is what we have changed:
- Cheaters will no longer be banned. Banning cheaters is great in theory, but the sheer volume of duplicate accounts which are created at the click of a button is testament to the fact that, in reality, it is an unenforceable policy. With our new policy we hope to strike a balance between making it clear to the community if someone has been caught cheating, and giving the cheater enough of an incentive not to create a duplicate account. Instead of banning cheaters we are introducing a new tagging system whereby there will be two types of tags -- red and orange. Those caught cheating will incur a red tag, which will be visible both on their profile (alongside further details) and behind every instance of their nickname. Those caught knowingly playing with Crossfire-tagged cheaters will incur an orange tag, which will be visible only on their profile. Those with red tags will not be allowed to play at Crossfire competitions, nor will they be able to create clans, post movies, or post in the recruitment forum. Other than this, their account will function as normal. A publicly viewable database listing those who are tagged is available here. A more comprehensive ignore feature will be added in a future Crossfire upgrade, and it will allow users to decide for themselves if they want to ignore tagged users.
The tag lengths will be as follows:
3 months for playing with cheaters; 6 months for cheating on a public server; 12 months for cheating in a clan match. Repeat offenders will get time-and-a-half.
- Spammers will no longer be banned. Those who persistently post spam, racism, adult material, or other disallowed content will have their posting rights temporarily revoked. During this time, they will still be able to use the site ordinarily. Bans will only be resorted to in extraordinary situations. As a result of this new policy, most of the ban list will be cleared.
- Report functionality for comments, content and users. This will enable users to report users for cheating, general rule-breaking, or otherwise, which should help Crossfire staff to run the site more efficiently. These rights will be revocable.
- Soft-deleting. Prior to 3.2, all deleted content disappeared into the ether, but, from now on most -- and soon all -- deleted content will be soft-deleted, instead, which means that deleted content can be restored. This will also make site staff more accountable for their actions, as it is now possible to see what was deleted, who deleted it, and when they deleted it.
- Extensive administrator logging. Practically every administrator action will be logged, increasing accountability.
- New userlevels. The following user levels will exist as of 3.2: Member; Tagged; Restricted (posting rights revoked); Trustee; News Writer; Moderator; Anti-cheat Administrator; Administrator; Head Administrator; Developer. This will help us run the site more efficiently, as the work will be delegated. This differs to the free-for-all that currently exists!
- The return of the search function!
- The return of the ajax inbox updater!
- Plenty of other cosmetic changes and bug fixes that you'll probably discover at some stage, too.
Given that we are clearing most of the ban list in an attempt to encourage users to stick to one account, I kindly request that anyone with a duplicate account (or ten!) report them so that they can be deactivated. This can be done by messaging either an administrator or head administrator on the members page, or by messaging an operator in #crossfire on QuakeNet. Nobody will be punished for having duplicate accounts if they report them to us.
On behalf of the Crossfire staff I'd like to express my gratitude to
4drenalin3 for making all of this possible. A big thank you also goes to 
krosan for his organisational work behind the scenes, and to 
Killerboy for his endless testing.Until Crossfire 3.3, enjoy!
nice btw...
I have proofs. PM
oh yeah, a person who talks shit all the time:ppPPppPP
olo
+1
yes i cann
And what will happen if I click report next to ur name?
Also, likewise with the previous version, if I click on a link externally for Crossfire it would ask me to login :-/
e:HF flagging all the cheaters killerboy.
e: sometimes it "plakt" on eachother, sometimes it's a grey button.
And the grey button is ugly.
Discrimination.
discrimination of polish contributers!!!
btw internal 500 error still here
edit: wow you're fast :)
awesome :)
This might keep the site clean from stupid comments and 'combo breakers'.
I wished they listened more to the visitors of the site instead of discussing within their own admin group. I had several other ideas in mind to improve cf.
:S
And, thank you 4drenalin3, having seen the CF codebase I know that there are more work behind this than most people realize! Kudos!
So we get updated
I like!
plus people should realize that this site needs some contributors. tosspot in the old days was one of the greatest contributors, but now isn't anymore. time someone steps up for him as a contributor.
1 of the 37 cool BRO!!!!
awesome update!
I'd prefer to have some sort of "user was banned in cb/esl for blablabla." and an extra field for "not allowed to participate in crossfire competitions until ______" instead of letting it disapear.
e: actually I think it would be better to show that info only in their profiles, cause those triangles all over the place are kinda annoying. especially since all those idiots are the worst spammers / trolls on cf
It might be better to tag, provide as much detail as possible such as ip, guid, and make their profile uneditable for this duration so original country, email, name etc is intact
it's a stupid idea
cheater
and other things, so in some way, cheaters can be mature.
another sample is chaplja.. you see him now helping the community. i hope other cheaters will follow his example ( not that every cheater needs to make a product like SLAC xD, that would be crazy :P )
My point was that cheating itself is immature. You cheated - thats wrong. Then after some time you started to help these guys, but that didn't erase what you had done earlier.
He cheated on other players and that's enough. Obviously it's just a game and that's why nobody is going to sentence him a death penalty, but that's not the point. He did wrong.
plz just change to "13 months for playing with cheaters;1 6 months for cheating on a public server; 112 months for cheating in a clan match. Repeat offenders will get time-and-a-half."
Internet Information Services 7.0
Error Summary
HTTP Error 500.0 - Internal Server Error
C:\Program Files (x86)\PHP\php-cgi.exe - The FastCGI process exceeded configured activity timeout
Detailed Error Information
Module FastCgiModule
Notification ExecuteRequestHandler
Handler PHP FastCGI
Error Code 0x80070102
Requested URL http://www.crossfire.nu:80/index.php?x=journal&mode=item&id=114349
Physical Path C:\inetpub\wwwroot\crossfire.nu\public_html\index.php
Logon Method Anonymous
Logon User Anonymous
Most likely causes:
* IIS received the request; however, an internal error occurred during the processing of the request. The root cause of this error depends on which module handles the request and what was happening in the worker process when this error occurred.
* IIS was not able to access the web.config file for the Web site or application. This can occur if the NTFS permissions are set incorrectly.
* IIS was not able to process configuration for the Web site or application.
* The authenticated user does not have permission to use this DLL.
* The request is mapped to a managed handler but the .NET Extensibility Feature is not installed.
Things you can try:
* Ensure that the NTFS permissions for the web.config file are correct and allow access to the Web server's machine account.
* Check the event logs to see if any additional information was logged.
* Verify the permissions for the DLL.
* Install the .NET Extensibility feature if the request is mapped to a managed handler.
* Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.
Links and More Information This error means that there was a problem while processing the request. The request was received by the Web server, but during processing a fatal error occurred, causing the 500 error.
View more information »
Microsoft Knowledge Base Articles:
* 294807
-_-
how gay
I mean, if you're new on cf and see the journal section, you'll most likely check the attracting stuff, and thus the bullshit posted by cheaters.
I think their journals should be with something like .5 alpha / transparency in the list, so we see them as not important.
You could do the same in comments, while keeping a rather visible /!\
- cheater makes a comment
- comment stays hidden unless you click on it ( like with the ignore function )
- that way most of them wont even be read/noticed by people
In my case for example I play with some busted cheaters (ex cheaters, I think most are LAN proven at this stage.) But say they were to be caught just now, I don't think I'd be able to find new friends to play with. I don't play with them because they are good, it's becaus I like and enjoy their company.
msg me. new year biatch