Re: [crossfire] stat loss and highly specialized players
Various quick notes: The target release varies depending on the change. For exp tables, I'd say that it can be put in 1.x as a commented out value, and if desirable, make it the default in 2.0 One thing to keep in mind in all these discussions is the relation of this lost with permanent exp. I think right now, whatever permanent exp you have earned does not affect the loss - it just means you can never have less than your permanent value. But if you die several ties relatively quickly, you can get down to that value pretty quickly. One change in this area could be to to base the experience loss based on the difference between current exp and permanent exp. Thus, for practical purposes, it would be very difficult to ever get all the way down to your permanent exp. But then I'm not sure if that would make any real difference (what could be interesting is having different permanent exp ratios for different skills). I think there will always be some issues with skill inequalities. Lets presume that under a revised system, you basically loose 1 level in each skill. That is certainly a lot better than it is now, but if you are level 80 in one handed fighting and level 10 in literacy, loosing that level in literacy will seem much harsher (in terms of actual character power/importance, level 79 vs 80 in fighting won't have a huge impact (in terms of percentage of actual level less, 9 vs 10 is bigger than 79 vs 80). Not sure how to fix that. One thing to keep in mind for the original tables is that they were done before we had 64 bit experience values. This put the limit at around 2 billion, which is why the hard table has that as the max exp. When the level array was increased to 115 with 64 exp values, the last 5 levels had a lot steeper curve because it could be done and to make it hard for people to max out their character. The old values were not changed for compatibility reasons. Because of that, as far as I can see, as long as the new exp total for level 115 is above that of the old value, there doesn't really need to be a big change in the curve for the final levels. I think under a revised system, you'll actually see fewer people at max levels, since it will be just as hard to get that much exp, so you are more likely to see characters sprinkled out amongst several levels when 100+ ___ crossfire mailing list crossfire@metalforge.org http://mailman.metalforge.org/mailman/listinfo/crossfire
Re: [crossfire] CVS - SVN conversion
Alex Schultz wrote: Mark Wedel wrote: Current status: CVS data is imported over, and I've renamed the files to be arch/trunk, client/trunk, etc. I've also made 1.x branches of the arch, client, maps, and server (at such time it becomes relevant, it could be done for jxclient and sounds). There are as arch/branches/1.x, client/branches/1.x, etc. snip So as of now, should we be committing to SVN as opposed to CVS, and using the 1.x branch and trunk as has been planned? :) Yes. In fact, I don't think anyone will be able to commit to CVS, as I've revoked everyones CVS access (seems only real way to prevent accidental checkins, etc) Btw, one thought is it would probably be good to make some sort of clear documentation for the usage of the 1.x branch and trunk and the branching plan. You mean like: http://wiki.metalforge.net/doku.php/crossfire_release_cycle That should probably be put someplace more prominently. ___ crossfire mailing list crossfire@metalforge.org http://mailman.metalforge.org/mailman/listinfo/crossfire
Re: [crossfire] CVS - SVN conversion
On Wed, 20 Sep 2006 00:02:48 -0700, Mark Wedel [EMAIL PROTECTED] wrote: [...] Yes. In fact, I don't think anyone will be able to commit to CVS, as I've revoked everyones CVS access (seems only real way to prevent accidental checkins, etc) Just a little note about that: those who used the developer access to CVS (over SSH) will find that operations like cvs update, cvs status or cvs diff do not work anymore. You have to change the CVS root and use the anonymous access instead of the developer access if you still want to check the status of your files or do a diff. I discovered this problem because although I had updated most of my checked out CVS trees last week, I saw yesterday that I forgot one of them. I wanted to do a cvs update or cvs status to check if I had any locally modified files or if I could just delete this tree, but the commands failed because the CVS access is now blocked for developers (cvs update fails because it cannot create the required lock file, so both the read and write access are effectively disabled). In case anyone here runs into the same problem and is unable to check the status of some old cvs trees, there is a simple solution: use a tool such as changecvsroot or changecvsroot.py (Python version handling subtrees in a better way) and replace :ext:[EMAIL PROTECTED]:/cvsroot/crossfire by :pserver:[EMAIL PROTECTED]:/cvsroot/crossfire in one go for your whole tree. This will now allow you to quickly check the status of your tree as an anonymous user and be sure that you can delete it without losing any locally modified files. -Raphaël ___ crossfire mailing list crossfire@metalforge.org http://mailman.metalforge.org/mailman/listinfo/crossfire
