[crossfire] 1.60 release thoughts
1.60.0 is close to being out the door, it might be by the time you read this message - after doing it, I've had various thoughts: - With SVN tree, all computer generated files get removed - I think the only thing really left is some of the macro files - since developers out of SVN are going to need autoconf/automake, pretty likely they will have aclocal/libtoolize, etc (in fact, I think those later ones are in autoconf or automake packages anyways) - Within the file release on sourceforge, I think it makes more sense to just have the version directories at the top (eg, 1.60.0, 1.50.0), and then under each one, put all the associated files - server, maps, client, different clines (linux, windows, java, etc). That would certainly be easier to navigate - very clear what the latest one is and no hunting for files. If we do get the case of some files not released (lets say we do an interim 1.61.0 for clients but not server), the readme there could note to use the 1.60.0 server. Thoughts? This becomes perhaps more relevant when jxclient and gridarta are added, as then there are lots of top level items. - At some point, the legacy character creation code should get removed, and related, basically all the ST_ values/player_set_state(). Anything that should have confirmation should be handled on the client, eg, if creating a party, should be an interface on the client to do that, which confirms the party password (and throws up an error if a mismatch), and it just sends the command to the server - maybe a protocol command for that, but there really isn't any reason password confirmations should be handled on the server. This just makes a much cleaner design - if a character is logged in, they are always playing. - For ChangeLog/CHANGES file: I suggest the ChangeLog file get generated by svn2cl - this is already done for maps. But each area also has a CHANGES file, which updated by hand but is used to note improvements/things of more general interest - hard to say where to really draw the line, but reformatting, minor bug fixes would not go in the CHANGES file - big features would. Maybe the determination is anything that actually affects gameplay? Thus, bug fixes wouldn't typically get put in (they may change gameplay because someone is exploiting a bug). One reason I bring this up is that with the maps ChangeLog file from SVN, really no way to get any real useful content from that - I pretty much used the crossfire traffic - it is that type of stuff that could perhaps get put in the CHANGES file. ___ crossfire mailing list crossfire@metalforge.org http://mailman.metalforge.org/mailman/listinfo/crossfire
[crossfire] Skill thoughts
I finally got around to recording my thoughts on a revised skill system: http://wiki.metalforge.net/doku.php/user:mwedel:skills Take a look, let me know what you think - as the bottom of the article says, I have no immediate plans to implement it - it is mostly thoughts that have been bouncing around my head that I wanted to record someplace. ___ crossfire mailing list crossfire@metalforge.org http://mailman.metalforge.org/mailman/listinfo/crossfire
[crossfire] crossfire-mapper
I wonder if I have forgotten how to run mapper, or if maybe something is broken. I was trying to update the website that has the generated data. Initializing Crossfire data... Unable to open /var/log/crossfire/logfile as the logfile - will use stderr instead Unable to open /var/log/crossfire/logfile as the logfile - will use stderr instead [Error] invalid smoothed face: fog_S.111 [Error] invalid smoothed face: grassmedium_S.111 [Error] Spell archetype abil_ball_lightning [ball lightning ability] has no skill defined! [Error] Spell archetype abil_burning_hands [burning hands ability] has no skill defined! [Error] Spell archetype abil_fear [fear ability] has no skill defined! [Error] Spell archetype abil_create_fire_wall [create fire wall ability] has no skill defined! [Error] Spell archetype abil_frostbolt [frostbolt ability] has no skill defined! [Error] Spell archetype abil_icestorm [icestorm ability] has no skill defined! [Error] Spell archetype abil_large_icestorm [large icestorm ability] has no skill defined! [Error] Spell archetype abil_medium_fireball [medium fireball ability] has no skill defined! [Error] Spell archetype abil_poison_cloud [poison cloud ability] has no skill defined! [Error] Spell archetype abil_slow [slow ability] has no skill defined! [Error] Spell archetype spell_shell [cannon shell] has no skill defined! Fatal: See last error Exiting... If anyone can confirm results or get different ones, I'd be interested in hearing about them. I'm thinking a readme file in the utils folder might be helpful. Kevin ___ crossfire mailing list crossfire@metalforge.org http://mailman.metalforge.org/mailman/listinfo/crossfire
Re: [crossfire] crossfire-mapper
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 1/29/11 9:24 PM, Kevin R. Bulgrien wrote: If anyone can confirm results or get different ones, I'd be interested in hearing about them. I'm thinking a readme file in the utils folder might be helpful. Make sure your archetypes are updated, as some of the Error messages you list were recently fixed. Then, run make collect in the server/lib directory. Compile the server once again. I did these two (well, three actually..) steps, and the error alerts you list were no longer a problem. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFNSh6thHyvgBp+vH4RArHxAKDSs1dTWIwMXURftEH49mMmrF9NYACgr1/V 7+zmVzEsTDG19U+sW7KTtFs= =7gD4 -END PGP SIGNATURE- ___ crossfire mailing list crossfire@metalforge.org http://mailman.metalforge.org/mailman/listinfo/crossfire
Re: [crossfire] crossfire-mapper
If anyone can confirm results or get different ones, I'd be interested in hearing about them. I'm thinking a readme file in the utils folder might be helpful. Make sure your archetypes are updated, as some of the Error messages you list were recently fixed. Then, run make collect in the server/lib directory. Compile the server once again. I did these two (well, three actually..) steps, and the error alerts you list were no longer a problem. Still mystified. arch is up-to-date showing mod dates in the last few days, and I did explicitly do make clean and make install in the lib folder as well as in the server area., and rebuild and reinstall server. If I look where the server is installed, the date/time of the crossfire.0 and .1 files is current. strace confirms the new file is in use at the location where the server is installed. I tried running crossfire-mapper from both the server/trunk/utils folder and from the server install location and from the templates folder under utils... all giving the same results. I suppose maybe it might help to see if there is an svn commit that seems to address those things and then try to correlate the change with the current generated content of the archetypes file in the server install. ___ crossfire mailing list crossfire@metalforge.org http://mailman.metalforge.org/mailman/listinfo/crossfire
Re: [crossfire] crossfire-mapper
Hello. Still mystified. arch is up-to-date showing mod dates in the last few days, and I did explicitly do make clean and make install in the lib folder as well as in the server area., and rebuild and reinstall server. If I look where the server is installed, the date/time of the crossfire.0 and .1 files is current. strace confirms the new file is in use at the location where the server is installed. Note the file you want to check is archetypes, since the crossfire.x files only contain pics :) make clean does not remove the lib/archetypes file, and won't collect, I just confirmed. As far as I can figure, the various make commands (except an explicit collect) are just happy with having a lib/archetypes file without checking the date. So I'd suggest to explicitely do ( cd lib make collect make install ) and try again. I tried running crossfire-mapper from both the server/trunk/utils folder and from the server install location and from the templates folder under utils... all giving the same results. I suppose maybe it might help to see if there is an svn commit that seems to address those things and then try to correlate the change with the current generated content of the archetypes file in the server install. Here's the revision that added that check: Revision: 14083 http://crossfire.svn.sourceforge.net/crossfire/?rev=14083view=rev Author: ryo_saeba Date: 2010-11-13 23:00:23 + (Sat, 13 Nov 2010) Log Message: --- Do not allow spells without a skill defined. Nicolas -- Mon p'tit coin du web - http://nicolas.weeger.org signature.asc Description: This is a digitally signed message part. ___ crossfire mailing list crossfire@metalforge.org http://mailman.metalforge.org/mailman/listinfo/crossfire
