[crossfire] Development Objectives.
Hi Team, You may have noticed that I have been furiously updating the content in the wiki (http://wiki.metalforge.net/doku.php). I have added a new section called "the sworn book of scorn" which is designed to be a reasonably detailed account of the way crossfire works without being a spoiler. I hope to make it useful to both new players and old players alike. Things like dumps from the archetypes would be useful but might crossover into spoilers so I haven't prioritised them. Aspects of game player that are described by code seem sensible items in this section. If anyone would like to help me read and interpret the code, I'd love some help! Come say hi on the IRC channel. What i'm actually writing about is that whilst working on this documentation I have 'stumbled' on the dev sections of the wiki. What a mess! Given that the Monk was my creation I have decided to go down a similar path to improving crossfire and develop a new class and at the same time improve the skill missle_weapons. The new class is currently slated as 'rangers' which are loosely outlined here: http://wiki.metalforge.net/doku.php/dev_todo:cf2.0:classes. Is this where such progress should be documented? I wasn't certain, so I tidied up the Dev front page a little.. however a lot of the pages seem to have been superseded and I can't make head nor tail of which is which. Perhaps it is timely to remap the direction of the game? I'm happy to assist in anyway to merge, fix, delete, update any pages that should be. In, particular one area of Dev interests me which is the Cf2.0 documents (which seem to start here: http://wiki.metalforge.net/doku.php/dev_todo:cf2.0) A lot of the ideas in here are absolutely fantastic and I would love to see them in game. Some of them seem quite straight forward whilst others seem very complicated. Is much progress happening towards these? Sorry for the long winded email Saru ___ crossfire mailing list crossfire@metalforge.org http://mailman.metalforge.org/mailman/listinfo/crossfire
Re: [crossfire] [RFC 2/3] Misc keybinding fixes and changes
I'd be of the view, if it isn't reducing a functionality but re-implementing it in a more useful way (be it more flexible, faster, or any other good reason) then it has my support. Perhaps another perspective is that if you change it, and things don't work out, it is a lot easier to backtrack and try and different approach, than it is to have abandoned the idea before anyone got to play with it and never know what we were missing in the first place :). I would mention that at the moment windows users are really limited to the jxclient, so do try and make a change that can be implemented on both the gtk and jxclient. Saru On Fri, Nov 1, 2013 at 10:24 AM, Kevin Zheng wrote: > Hi there, > > On 10/30/2013 20:06, Arvid Brodin wrote: > > As a new player, I found this to be a usability problem. Everyone knows > what > > the Control key is, but what's the Run key? I think the reason Shift and > Ctrl > > were called Fire and Run is that it is possible to rebind them - i.e. if > you > > want some other key to act as the Run modifier, you could > > > > 'bind runkey1 > > I wasn't aware that this "feature" even existed. If it isn't present in > the JXClient, I'd say it's safe to take it out. > > > - and press a key to act as the Run modifier. (Actually I'm not even > sure this > > worked; I never tried it - and I'm pretty sure it requires the run_on > state to > > be kept in the server, since key repeats won't work if you bind Run to, > say, > > 'r', and press that after the direction key... hmm. So it might be in > the way > > of better handling of repeating keys.) > > Probably not, repeating keys should be handled more elegantly. > > > I realize this change might not be liked by everyone, so feel free to > shout out > > in that case (RFC = Request For Comments). But it did seem like a pretty > unique > > and not very well advertised feature, so I chanced that it could be > removed. > > You have my vote to take it out. Input from others would be helpful. > > Thanks, > Kevin Zheng > ___ > 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
Re: [crossfire] [RFC 2/3] Misc keybinding fixes and changes
Hi there, On 10/30/2013 20:06, Arvid Brodin wrote: > As a new player, I found this to be a usability problem. Everyone knows what > the Control key is, but what's the Run key? I think the reason Shift and Ctrl > were called Fire and Run is that it is possible to rebind them - i.e. if you > want some other key to act as the Run modifier, you could > > 'bind runkey1 I wasn't aware that this "feature" even existed. If it isn't present in the JXClient, I'd say it's safe to take it out. > - and press a key to act as the Run modifier. (Actually I'm not even sure this > worked; I never tried it - and I'm pretty sure it requires the run_on state > to > be kept in the server, since key repeats won't work if you bind Run to, say, > 'r', and press that after the direction key... hmm. So it might be in the way > of better handling of repeating keys.) Probably not, repeating keys should be handled more elegantly. > I realize this change might not be liked by everyone, so feel free to shout > out > in that case (RFC = Request For Comments). But it did seem like a pretty > unique > and not very well advertised feature, so I chanced that it could be removed. You have my vote to take it out. Input from others would be helpful. Thanks, Kevin Zheng ___ crossfire mailing list crossfire@metalforge.org http://mailman.metalforge.org/mailman/listinfo/crossfire
