I think the webpage idea isn't very good - most people will simply ignore/dismiss them. I'd rather see "harmless" scripts get directly into the python subdirectory of the map repository, while the more controversial ones could get into an optional package, available at the same download location as the maps or the server. Controversed scripts could also get into /maps/python-optional - even if it means people will download some files they'll never use, I think that the space overhead is really negligible.
As long as the added functionalities don't disturb the play balance (and are not too bugged :)), I think they should get into the maps CVS repository. That's exactly what we do when we add new functionalities coded in C, so there's no reason to handle this differently. -----Original Message----- From: Nicolas Weeger <[EMAIL PROTECTED]> To: Crossfire Discussion Mailing List <crossfire@metalforge.org> Date: Sun, 15 Jan 2006 14:45:42 +0100 Subject: [crossfire] (Python) script distribution Hello. There are a few (Python) scripts i'd like to write, to extend Crossfire. Merely thinking something like a "visit card" system (to let other players know your level or skill), or something to autorejoin party at login time. So I'm wondering where to put those scripts. Should I put them in the python subdirectory in maps, and assume everyone will want them? Should we create a new subdirectory with "optional scripts"? Should I put'em on some web page and let interested people download? Note that this can in some ways apply to existing scripts (occidental stuff scripts, for instance). I'd say either put in python subdir, or create a new subdirectory - it's the simplest way to distribute things imo. Nicolas _______________________________________________ crossfire mailing list crossfire@metalforge.org http://mailman.metalforge.org/mailman/listinfo/crossfire _______________________________________________ crossfire mailing list crossfire@metalforge.org http://mailman.metalforge.org/mailman/listinfo/crossfire
