翻译帝来吧，XJ新文章又出了（好了删掉鹰文看着头疼）

e3fb123

Hey guys,

as announced in an earlier newspost the old mapcheck team got released from their duty and the old mapcheck system as we knew it stopped existing.

In the meantime we had an internal discussion about possible solutions to this - and right now I'd like to present our possible soltions for this huge problem to you, giving you guys a chance to raise your voice and contribute to solve this. Mapreleases have been an important part of this community ever since it started to exist, therfore everyone of you should feel responsible for this. There is also going to be a public vote, to evaluate the different opinions in the community - at the same time we're going to have an internal vote; and after all votes were evaluated we're going to announce what is going to happen to the mapcheck system.
Please make sure you read all of the detailed explanations before you do your vote, because you obviously got to know what you are voting for.

Note: The vote is going to start tomorrow, in the meantime we would kike to give you guys the chance to suggest different ideas (which might be added to the poll as well).

1. Free KZ_ tag (XJ adding good maps to the so called "mapcycle")

This would mean that everyone has the right to release his map with the kz_ tag right away in a forum called "mapreleases". XJ would be browsing this forum every 14 days and pick the most popular (most downloaded and most played) maps out of the forum and adds them to the record section.

+ More freedom for the community/mappers
+ No more mapcheck team needed, adding the maps due to their popularity within the community
- More chaos regarding mapfixes and different versions: Maps might get released with bugs, then get fixed afterwards with the same name, causing different versions of the map with the same mapname.
- Acting against Kreedz's original idea he had for the community/mapcheck system
- Decreasing quality, kz_ wont be a "grade" for quality anymore.
- No way back


2. Going back to the old Kreedz system

Going back to the old Kreedz.com system would mean putting one or two persons (the most experienced persons available - but who are they?) in charge of the maps. Submitted maps get checked by them without having to coordinate a whole team and without having to justify their votes. Good maps get released at a time of their choice, bad maps don't get released. When needed, they talk to the mappers in private - however you can't expect detailed feedback or huge help at all, regarding the high numbers of mapsubmissions and their recent quality.

+ Easier to arrange and faster results
+ Easier contact between the admins and the mappers, admins can speak out without having to sum up the opinions of the other admins and justify their votes
- Huge power and huge responsibility for a single person or persons, therfore a huge pressure
- More "fragile" when it comes to recriminations about "being friends with the mappers" and "being unfair"
- If the few persons leave into inactivity without looking out for other admins replacing them, the whole system might die


3. Public open-beta mapchecking

This is NOT the same as the "public mapchecking" we tryed before. In this idea mappers would be able (not forced!) to post their maps into a forum called "public mapchecks". Every player of the whole community (no applications needed) could download and test the maps, and later give some feedback about it (report bugs, shortcuts, problems). The map would have to be called bkz_faker_b01, for example, during that time (if some bugs get fixed b02 and so on). Once the mapchecking is done, the mapper has to submit the map to XJ as usual, but they do very quick votes on the maps (after checking the popularity of the map during the test) and release the map (or deny it)... The XJ "mapadmins" would be picked from those testers who contribute the most. If a mapper doesn't want to use the public open-beta he can do that, but if he submits the map with bugs and it gets denied because of them, it is his problem and he has to live with it (no chance to re-submit maps that weren't posted in the open-beta system). So if you don't want to use the system, it's your responsibility to get some friends to test the maps for bugs in a closed beta and submit it once it is finished.

+ No more detailed feedbacks to sum up, no more explanations, just a simple and pure process of adding the maps according to their quality and popularity after the public beta.
+ No more (or at least less) checking of "fixed versions"
+ Chance to get an admin position by contributing to the tests for every user
- Less surprise because most mappers will use the public beta forum
- Dependent on how motivated the people (you, the community) are - may depend up on map quality and season (in the summer less people play etc.). People could be rude to mappers who submit bad quality maps or just ignore them, because they are boring.



4. Custom-mapreleases

Pretty much another version of the free kz_ tag. All maps have to be released as custom maps (called bkz_goldbhop for example), and XJ gives out the kz_ tag after a while if the maps are popular.

+ One internal "vote" (regarding the popularity of the map) about a map that has been released already
+ No more detailed feedbacks to sum up, no more explanations, just a simple process of adding the map if it is good
- No surprise effect anymore, not even for great maps
- All good maps would have to be renamed (custom -> kz_*). Demos that were recorded with the old name would be not legit?



5. Old system with mappers and record holders involved as mapcheck admins

Pretty much obvious, the old mapcheck system with current mappers and record holders as admins. Nobody is forced to vote, the majority of those who voted wins.

+ A way of "public" mapchecking, everyone who wants to contribute can do it.
+ Opinions from experienced people. People gotta earn their right to vote by making an effort
- People could make biased votes for their friends
- Maps could get leaked very easily, therfore no big surprises.

gyssi

火速翻译！！！！

lovehuai

google 在线翻译貌似懂了个大概

1. 嗨，
   
2. 
   
3. 作为较早newspost旧mapcheck车队宣布了免除其责任和旧mapcheck系统，我们知道它停止存在。
   
4. 
   
5. 与此同时，我们有一个关于这个内部讨论可能的解决办法 - 而且现在我想现在这个大问题，给你的可能soltions，让你们有机会提高你的声音，并有助于解决这个。 Mapreleases一直是这个社区的重要组成部分开始以来就存在，你therfore每个人都应该对此感到非常负责任的。也有将是一个公众投票，以评估在社会上不同的意见 - 在同一时间我们将有一个内部票;并且是在所有选票进行了评价，我们将要宣布什么事情发生到mapcheck系统。
   
6. 请确保您阅读的详细解释都在这样做之前你的投票，因为你显然知道了你的投票选举。
   
7. 
   
8. 注：投票明天将开始在此期间，我们将kike让你们有机会提出不同意见（这可能是添加到调查以及）。
   
9. 
   
10. 1。免费kz_标签（许继加上良好的映射到所谓的“mapcycle”）
    
11. 
    
12. 这意味着，每个人都有权利释放与kz_他的地图标记马上在一个论坛上被称为“mapreleases”。许继将浏览此论坛的每14天，然后从中选出最流行（下载次数最多，最扮演）论坛的地图出来并将它们添加到记录部分。
    
13. 
    
14. +更多的自由社会/映射
    
15. +没有更多的mapcheck球队需要，增加社区内的地图，因为它们受欢迎
    
16. - 关于mapfixes更多的混乱和不同的版本：地图可能会发布了漏洞，然后得到固定的具有相同名称后，导致具有相同mapname地图的不同版本。
    
17. - 代理对Kreedz的理念，他为社区/ mapcheck系统
    
18. - 降低质量，kz_ wont是一个“等级的质量”了。
    
19. - 不归路
    
20. 
    
21. 
    
22. 2。让我们回到旧Kreedz系统
    
23. 
    
24. 让我们回到旧Kreedz.com系统，这意味着将一个或两个人（最有经验的人士提供 - 但他们是谁？）在地图的费用。检查提交的地图让他们不必协调整个球队，而无需证明自己的选票。好图得到发表在自己选择的时间，糟糕的地图没有得到释放。当需要时，他们私下交谈的映射 - 但是你不能指望在所有详细的反馈或巨大的帮助，关于mapsubmissions高数目及最近的品质。
    
25. 
    
26. +更容易和更快的结果安排
    
27. +更方便管理员之间的映射和联系，管理员可以说出来，而不必总结其他管理员的意见，证明他们的选票
    
28. - 巨大的权力，一个人或一个人的重大责任，therfore一个巨大的压力
    
29. - 更多“脆弱”，当涉及到相互指责对“与映射是朋友”和“不公平”
    
30. - 如果少数人的情况下离开无所作为寻找其他管理员更换他们指出，整个系统会死
    
31. 
    
32. 
    
33. 3。公众休憩-βmapchecking
    
34. 
    
35. 这是不一样的“公共mapchecking”我们tryed前。在这一思想映射就可以（不强迫！）后进入所谓“公共mapchecks论坛的地图”。每一个对整个社会的球员（没有应用程序需要）可以下载和测试的地图，后来提供一些反馈信息，它（报告错误，快捷，问题）。该地图将被称为bkz_faker_b01，例如，在这段时间里（如一些bug得到修复b02等）。一旦mapchecking做，映射器须提交图许继像往常一样，但他们在地图上很快票（检查后，在测试期间的地图受欢迎），并释放地图（或拒绝）.. 。在许继“mapadmins”会挑选那些测试谁贡献最大。如果一个映射程序不希望使用公共开放测试，他能做到这一点，但如果他提出了错误的地图和与它获取，因为他们否认，这是他的问题，他有良好的表现（无机会重新提交的没有在开放测试系统发布地图）。所以，如果你不想使用这个系统，是你的责任就是让一些朋友测试在封闭测试阶段的错误的地图，并提交一旦完成。
    
36. 
    
37. +无更详细的反馈，总结，没有更多的解释，只是加入的公开测试后的地图根据它们的质量和知名度单纯的过程。
    
38. +没有更多的（或至少）“固定版本检查”
    
39. +机会获得捐款为每个用户的测试管理员立场
    
40. - 减惊讶，因为大多数映射器将使用公开测试论坛
    
41. - 如何激励依赖的人（你，社会）是 - 可能取决于地图质量和季节了（在夏季少人玩等）。人们可以很不礼貌映射质量差，谁提交的地图或不理会他们，因为他们是无聊。
    
42. 
    
43. 
    
44. 
    
45. 4。定制mapreleases
    
46. 
    
47. 几乎另一个版本的自由kz_标记。所有的地图都必须公布自定义地图（称为bkz_goldbhop例如），以及XJ了一段时间后，如果给kz_标记的地图很受欢迎。
    
48. 
    
49. +一个内部的“投票”（关于地图的普及），大约已经公布了地图
    
50. +无更详细的反馈，总结，没有更多的解释，只是在地图上添加简单的过程，如果是好的
    
51. - 没有意外的效果了，甚至没有伟大的地图
    
52. - 所有好的地图将被重新命名（自定义 - “kz_ *）。演示录得的与旧的名称将不正统剧？
    
53. 
    
54. 
    
55. 
    
56. 5。旧制度与映射和mapcheck管理员纪录保持者参与
    
57. 
    
58. 几乎明显，与目前的映射和管理员纪录保持者旧mapcheck制度。没有人强迫投票，那些投谁赢得多数。
    
59. 
    
60. +一个“公有”mapchecking这样，大家谁愿意贡献可以做到。
    
61. +的意见，由有经验的人。人们gotta获得他们的投票权作出的努力
    
62. - 人们可以为自己的朋友有偏见的投票
    
63. - 图可以得到很容易泄露，therfore没有大的意外。
    

复制代码

SiMen.Jc

晓得我是阴文盲~~

TrageDy

哦,地图检测小组解散了,以后有做图人传新图就让玩家试玩,然后觉得好的就可以作为官方图......

fanzhen0019

关于地图 看见Kreedz了

谷歌是不可靠的

Pepent

谷歌果然不坚挺。。下次得用谷姐..

fanzhen0019

大概搞懂了 感谢3L


嗨，
作为较早newspost旧地图检测小组宣布了免除其责任和旧mapcheck系统，我们知道它已经不存在了。 (XJ地图小组解散?)
与此同时，我们有一个关于可能的解决办法 - 而且现在我想和你们说一下关于这个问题的解决方案，giving you guys a chance to raise your voice (???)，并有助于解决这个问题。 地图发布 一直XJ的重要组成部分而且开始以来就存在，所以每个人都应该对此感到非常负责任的。也有将是一个公众投票，以评估在XJ上不同的意见 - 在同一时间我们将有一个内部投票;所有选票会被评论，之后我们会宣布mapcheck系统会发生什么事情。
请确保在你投票前之前你已阅读所有详细解释，因为你显然知道了你的投票是干什么。
注：投票明天将在此期间开始，我们将让你们有机会提出不同意见（这可能也会添加到调查）。

1。自由的kz_ 标签（XJ会加好图到所谓的“mapcycle”）
这意味着每个人的地图都可以使用kz_前缀 地图会发布在一个论坛上被称为“mapreleases”。XJ将浏览这个版块14天，然后从中选出最流行（下载次数最多，玩得最多）的地图出来并将它们添加到记录部分。

编辑中

SiMen.Ateman

这个不是新闻吧 我早看过了

rongwenfeng

哎！！KZ这个游戏还能走多远？