Re: [crossfire] Re: [Crossfire-devel] Made a CVS upload error: /maps-bigworld/unlinked/mlab-devel/mlab-devel.tar.gz
If you don't want mlab then fine. I am _not_ going to change for you, just as you are _not_ going to change for me. --- Mark Wedel <[EMAIL PROTECTED]> wrote: > Mitch Obrian wrote: > > For all other maps sans mlab I follow the map > guide. > > However mlab was started way before these, thus it > > uses the flatdirectory structure so it stays > working. > > I've seen maps break many times before, including > my > > tavern when it was uploaded to cvs originally. > > The issue is that there seems to be no work on > your part to move it into the > proper directory layout. > > If there was some progess being made in going to a > non flat structure, > wouldn't be a big deal. > > > > > Why must there be contoversy just over a file > system? > > Ask yourself the same question - why can't you fix > them so they aren't in a > flat directory. > > > > > If I can't upload my maps to CVS where do I back > them > > up to? Are they that worthless? I do a fair amount > of > > CF work in arches and non-mlab maps, could I have > > alittle slack? Why is there opposistion just > because I > > put the maps in their own flatlevel dir? > > Sourceforge and the crossfire distribution in > particular is not meant to > provide a backup service for people. > > There are standard practices for a reason. The > second exceptions start > getting made for one person, the next person shows > up and says 'well, you did it > for him, why not for me'. And figuring out what > rules to break for who then > leads to a mess of problems. > > > > > The reasoning that mlab doesn't even deserve to be > in > > CVS is very alienating, I've worked years on > theses > > maps. I work nearly constantly on maps for CF. > > I don't think I said it doesn't deserve to be in > CVS. I've just said that if > it is in CVS, it should follow proper standards. > > > > > Mlab could be intergrated into CF-proper right now > if > > I was just given the OK. If an exception to the > dir > > rule was made. > > > > I though after being involved in CF this long the > > controversy was over and I could develop as a > regular > > without asking about every change. I uploaded mlab > so > > it would be with CF, so if my computers go down my > > years of work are not lost. Sure one can say "go > find > > some other place to back up to" but... that's > > basically telling the person to screw off; their > work > > is of little value. > > Simple solution is that if you make the directory > structure follow the proper > naming, it could be an official part of the map > distribution. > > The only issue is that your completely unwilling > to do that. Some people have > even started the work to integrate your maps with > proper naming structure, but > you continue to keep going with yours (so that even > those get updated). > > Sure, we could make an exception. Or you could > just follow the rules. The > fact that your not willing to make any effort to do > so doesn't give me any > reason whatever on why I should bend the rules for > you. > > > ___ > crossfire mailing list > crossfire@metalforge.org > http://mailman.metalforge.org/mailman/listinfo/crossfire > __ Yahoo! for Good Donate to the Hurricane Katrina relief effort. http://store.yahoo.com/redcross-donate3/ ___ crossfire mailing list crossfire@metalforge.org http://mailman.metalforge.org/mailman/listinfo/crossfire
Re: [crossfire] Summon pet monster
> If so: that probably would not be correct. According to the comment for > this function, "!new_skill" means to just unapply the old skill. > Therefore the call to apply_special(..., AP_UNAPPLY) must not be > removed. Yes, of course you're right. I realize that after sending my message. Benjamin Lerman ___ crossfire mailing list crossfire@metalforge.org http://mailman.metalforge.org/mailman/listinfo/crossfire
Re: [crossfire] Re: [Crossfire-devel] Made a CVS upload error: /maps-bigworld/unlinked/mlab-devel/mlab-devel.tar.gz
Let us free our memory of merging the rest of mlab, it just seems to become a huge discussion for whatever reasons. So have any quest ideas for azamuindo? I need someone who has a good grasp on japanese lore to give me some ideas. --- Mitch Obrian <[EMAIL PROTECTED]> wrote: > If you don't want mlab then fine. I am _not_ going > to > change for you, just as you are _not_ going to > change > for me. > > --- Mark Wedel <[EMAIL PROTECTED]> wrote: > > > Mitch Obrian wrote: > > > For all other maps sans mlab I follow the map > > guide. > > > However mlab was started way before these, thus > it > > > uses the flatdirectory structure so it stays > > working. > > > I've seen maps break many times before, > including > > my > > > tavern when it was uploaded to cvs originally. > > > > The issue is that there seems to be no work on > > your part to move it into the > > proper directory layout. > > > > If there was some progess being made in going to > a > > non flat structure, > > wouldn't be a big deal. > > > > > > > > Why must there be contoversy just over a file > > system? > > > > Ask yourself the same question - why can't you > fix > > them so they aren't in a > > flat directory. > > > > > > > > If I can't upload my maps to CVS where do I back > > them > > > up to? Are they that worthless? I do a fair > amount > > of > > > CF work in arches and non-mlab maps, could I > have > > > alittle slack? Why is there opposistion just > > because I > > > put the maps in their own flatlevel dir? > > > > Sourceforge and the crossfire distribution in > > particular is not meant to > > provide a backup service for people. > > > > There are standard practices for a reason. The > > second exceptions start > > getting made for one person, the next person shows > > up and says 'well, you did it > > for him, why not for me'. And figuring out what > > rules to break for who then > > leads to a mess of problems. > > > > > > > > The reasoning that mlab doesn't even deserve to > be > > in > > > CVS is very alienating, I've worked years on > > theses > > > maps. I work nearly constantly on maps for CF. > > > > I don't think I said it doesn't deserve to be in > > CVS. I've just said that if > > it is in CVS, it should follow proper standards. > > > > > > > > Mlab could be intergrated into CF-proper right > now > > if > > > I was just given the OK. If an exception to the > > dir > > > rule was made. > > > > > > I though after being involved in CF this long > the > > > controversy was over and I could develop as a > > regular > > > without asking about every change. I uploaded > mlab > > so > > > it would be with CF, so if my computers go down > my > > > years of work are not lost. Sure one can say "go > > find > > > some other place to back up to" but... that's > > > basically telling the person to screw off; their > > work > > > is of little value. > > > > Simple solution is that if you make the > directory > > structure follow the proper > > naming, it could be an official part of the map > > distribution. > > > > The only issue is that your completely unwilling > > to do that. Some people have > > even started the work to integrate your maps with > > proper naming structure, but > > you continue to keep going with yours (so that > even > > those get updated). > > > > Sure, we could make an exception. Or you could > > just follow the rules. The > > fact that your not willing to make any effort to > do > > so doesn't give me any > > reason whatever on why I should bend the rules for > > you. > > > > > > ___ > > crossfire mailing list > > crossfire@metalforge.org > > > http://mailman.metalforge.org/mailman/listinfo/crossfire > > > > > > > > __ > > Yahoo! for Good > Donate to the Hurricane Katrina relief effort. > http://store.yahoo.com/redcross-donate3/ > > > ___ > crossfire mailing list > crossfire@metalforge.org > http://mailman.metalforge.org/mailman/listinfo/crossfire > __ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com ___ crossfire mailing list crossfire@metalforge.org http://mailman.metalforge.org/mailman/listinfo/crossfire
Re: [crossfire] Summon pet monster
Committed your 2 patches. Just changed one call from (pseudo variables) (x)?f(a,b,c):f(a,b,d) to f(a,b,x?c:d) to not duplicate 2 similar calls Nicolas ___ crossfire mailing list crossfire@metalforge.org http://mailman.metalforge.org/mailman/listinfo/crossfire
Re: [crossfire] Re: [Crossfire-devel] Made a CVS upload error: /maps-bigworld/unlinked/mlab-devel/mlab-devel.tar.gz
Why don't you create a new Sourceforge project and use it to store your maps? This way you'll have storage room, cvs, and will be able to use the structure you want :) Nicolas ___ crossfire mailing list crossfire@metalforge.org http://mailman.metalforge.org/mailman/listinfo/crossfire
Re: [crossfire] Re: [Crossfire-devel] Made a CVS upload error: /maps-bigworld/unlinked/mlab-devel/mlab-devel.tar.gz
A new module would be simpler, but perhapse. --- Nicolas Weeger <[EMAIL PROTECTED]> wrote: > Why don't you create a new Sourceforge project and > use it to store your > maps? > This way you'll have storage room, cvs, and will be > able to use the > structure you want :) > > Nicolas > > ___ > crossfire mailing list > crossfire@metalforge.org > http://mailman.metalforge.org/mailman/listinfo/crossfire > __ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com ___ crossfire mailing list crossfire@metalforge.org http://mailman.metalforge.org/mailman/listinfo/crossfire
