User map imports

[bort]

I think an auto-reject feature would work, like

Code: Select all

 item sword in hp 24, sp 2, has arch ukswd. rejecting.

[Avion]

I don't really see any need to automate this - if you know a server admin for a crossfire server and gain their trust through long and favourable interactions you can arrange to upload maps to their server no problem. Another route is to submit maps to CVS. Building a secure system to automate this in the server would be a series of long and kludgy steps IMHO. Even heavily tested maps can have bugs or exploits in them.
There are so many other things to do that this seems like a real make work type thing. Likely this indicates it will be done sooner than critical bug fixes .

[bort]

Easy for you to say. If I made a perfect, acceptable map, I'd still have a hell of a time getting it in to the examing side, and sometimes, these maps are never even looked at. So the procedure of going through a server admin seems outrageous to me. Not to mention, the metalforges DM's would not trust me with a simple sabre.

Solution:
There needs to be the map squad, a team that actually checks submitted maps and actually gives feedback, at least saying "Will not be accepted', or "Will be Accepted."
Then, map creators can improve their maps, or get feedback.

[Leaf]

Not to mention, the metalforges DM's would not trust me with a simple sabre.

I wonder what brought that on... Hmm, maybe not.

Solution:
There needs to be the map squad, a team that actually checks submitted maps and actually gives feedback, at least saying "Will not be accepted', or "Will be Accepted."
Then, map creators can improve their maps, or get feedback.

Maps are checked.. but how good of a test is one server or person?

Until enough people volunteer or a team is organized, here's my suggestions on what to do in the mean time:

1.) Design or create a map, fix or update an existing map

2.) Make sure the map meets the requirements specified in the Map Guide
http://crossfire.real-time.com/guides/map/index.html

3A.) Test it on a local (aka private or LAN) server
3B.) Coordinate with a public server admin so that the map in question can be uploaded and tested on that server
NOTE: looks like one is availabe - http://crossfire.schmorp.de/

4.) Assuming the map does not have any outstanding issues or problems, upload the map to the SourceForge Patch area http://sourceforge.net/tracker/?group_i ... tid=313833
4.1) If fixing or updating a map, be sure to explain what is being fixed/updated and why
4.2) Be sure to specify which CVS date or server version the map was tested against
4.3) Include a md5 sum with the map

5.) Hope/wait* for other public servers to make the maps available
* More details need to be worked out on this part...

6.) As a map developer, be responsive to comments and suggestions
6A.) Server admins - provide comments, suggestions and feedback
6B.) Players - test out these maps and be ready to provide comments, suggestions and feedbacks directly to the SF Patch area (don't make DM's or other server admins relay the message for you)

I'm sure there are more details to address, but this is a rough draft.