Re: [crossfire] Crossfire Client 1.72.0 is available
are you niggas still going god damn just grind on some crossfire On Aug 19, 2017 5:11 PM, "Preston Crow"wrote: > That would be a great solution. > > > On 08/19/17 12:10, Kevin Zheng wrote: > >> On 08/19/2017 04:59, Preston Crow wrote: >> >>> What would be really cool is a command-line option to start a client >>> script, especially if it could be used multiple times for multiple >>> scripts. (I normally launch two.) >>> >> Maybe like a login.rc file that gets read as soon as the character >> enters the game? >> >> > ___ > 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] Crossfire Client 1.72.0 is available
That would be a great solution. On 08/19/17 12:10, Kevin Zheng wrote: On 08/19/2017 04:59, Preston Crow wrote: What would be really cool is a command-line option to start a client script, especially if it could be used multiple times for multiple scripts. (I normally launch two.) Maybe like a login.rc file that gets read as soon as the character enters the game? ___ crossfire mailing list crossfire@metalforge.org http://mailman.metalforge.org/mailman/listinfo/crossfire
Re: [crossfire] Crossfire Client 1.72.0 is available
On 08/19/2017 04:59, Preston Crow wrote: > What would be really cool is a command-line option to start a client > script, especially if it could be used multiple times for multiple > scripts. (I normally launch two.) Maybe like a login.rc file that gets read as soon as the character enters the game? -- Kevin Zheng kevinz5...@gmail.com | kev...@berkeley.edu | PGP: 0xC22E1090 ___ crossfire mailing list crossfire@metalforge.org http://mailman.metalforge.org/mailman/listinfo/crossfire
Re: [crossfire] Crossfire Client 1.72.0 is available
What would be really cool is a command-line option to start a client script, especially if it could be used multiple times for multiple scripts. (I normally launch two.) On 08/19/17 01:26, Kevin Zheng wrote: On 08/18/2017 20:28, Preston Crow wrote: The "cleanup" of command line options seems to have removed almost all of them, including many useful ones. There isn't even an option for selecting the server anymore! I really need the mapscale and iconscale options for high DPI displays--those have also been removed from the UI settings. Sorry about that; I'll work on adding them back. In the meantime, edit ~/.config/crossfire/client.ini ___ crossfire mailing list crossfire@metalforge.org http://mailman.metalforge.org/mailman/listinfo/crossfire
Re: [crossfire] Crossfire Client 1.72.0 is available
On 08/18/2017 20:28, Preston Crow wrote: > The "cleanup" of command line options seems to have removed almost all > of them, including many useful ones. There isn't even an option for > selecting the server anymore! I really need the mapscale and iconscale > options for high DPI displays--those have also been removed from the UI > settings. Sorry about that; I'll work on adding them back. In the meantime, edit ~/.config/crossfire/client.ini -- Kevin Zheng kevinz5...@gmail.com | kev...@berkeley.edu | PGP: 0xC22E1090 ___ crossfire mailing list crossfire@metalforge.org http://mailman.metalforge.org/mailman/listinfo/crossfire
Re: [crossfire] Crossfire Client 1.72.0 is available
On 08/15/2017 09:45 PM, Ruben Safir wrote: On Tue, Aug 15, 2017 at 09:03:44PM +1000, David Hurst wrote: Just wanted to add my 2 cents and say that anything that makes the client more accessible on windows is a big plus to me. Even though i'm happy to set the game up on linux, most of my friends are not, by offering support to windows we can gain access to a larger player base. I don't want to beat a dead horse but I just want to say that this logic has NEVER worked out in almost 30 years now. It will not cause a larger player base. Installing Linuix, however, does. CMake works perfectly on Linux and will help Crossfire to be more portable on Windows. TBH, I don't understand your point at all. btw: Good job, Kevin and many thanks! ___ crossfire mailing list crossfire@metalforge.org http://mailman.metalforge.org/mailman/listinfo/crossfire
Re: [crossfire] Crossfire Client 1.72.0 is available
On Tue, Aug 15, 2017 at 09:03:44PM +1000, David Hurst wrote: > Just wanted to add my 2 cents and say that anything that makes the client > more accessible on windows is a big plus to me. Even though i'm happy to > set the game up on linux, most of my friends are not, by offering support > to windows we can gain access to a larger player base. I don't want to beat a dead horse but I just want to say that this logic has NEVER worked out in almost 30 years now. It will not cause a larger player base. Installing Linuix, however, does. > > Regards, > Saru > > On Tue, Aug 15, 2017 at 3:22 PM, BloodyShadewrote: > > > On 8/15/2017 2:00 AM, Ruben Safir wrote: > > > >> On 08/14/2017 05:39 PM, Kevin Zheng wrote: > >> > >>> . If you play, > >>> but use a package from your OS, I don't see how this impacts you. > >>> > >> > >> I compile it > >> > >> and I don't think there is a package. I hate cmakes license, and I'm > >> not found of its syntax either. > >> > >> I'm just generally sick of BSD junk being forced on me, and FWIW, if it > >> never compiles on Windows, that is fine as well. > >> > >> > >> > >> > > So you'd rather make it both harder to maintain and less platform > > independent for others just because of your ideological standpoint in > > regards to licenses and some minor inconvenience of installing a few more > > packages? > > > > Also, as Kevin said, you can keep using the old system and adapt it to > > your own needs, nobody is forcing anything on anybody here. > > > > Back when I used to play, I had to change things in the source and > > basically rewrite the msvc project completely to be able to compile it on > > windows xp/7 at the time. > > Kevin might even remotely remember me, since I reported many ansi c (and > > other) issues, which I found during that time. > > > > In short, making the source more platform independent and easier to > > maintain for the current maintainers sound like a good step forward to me. > > > > Regards, > > BloodyShade > > > > ___ > > 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 -- So many immigrant groups have swept through our town that Brooklyn, like Atlantis, reaches mythological proportions in the mind of the world - RI Safir 1998 http://www.mrbrklyn.com DRM is THEFT - We are the STAKEHOLDERS - RI Safir 2002 http://www.nylxs.com - Leadership Development in Free Software http://www2.mrbrklyn.com/resources - Unpublished Archive http://www.coinhangout.com - coins! http://www.brooklyn-living.com Being so tracked is for FARM ANIMALS and and extermination camps, but incompatible with living as a free human being. -RI Safir 2013 ___ crossfire mailing list crossfire@metalforge.org http://mailman.metalforge.org/mailman/listinfo/crossfire
Re: [crossfire] Crossfire Client 1.72.0 is available
The 1.72.0 client build for Windows is now available on SourceForge: https://sourceforge.net/projects/crossfire/files/crossfire-client/1.72.0/ Some network issues were fixed between the latest snapshot and the 1.72.0 client, so you should upgrade when convenient. Hash: SHA256 SHA256 (crossfire-client-1.72.0.tar.bz2) = 2e863f09be0d5480708e031afb212361f58f6827a68120ffef075b94406d73a5 SHA256 (crossfire-sounds-1.72.0.tar.bz2) = b41fbac33cbffb6850bbe497ac4d1bcbf5e514073e288f4b00af0c10e99c1d62 SHA256 (crossfire-client-1.72.0-winx86_64.zip) = cd3ef354d5222598e94b82cfefa0cb4fffd8557fc825ca5250f59df053743365 Precompiled pixmaps will not be provided for this release. Regards, Kevin -- Kevin Zheng kevinz5...@gmail.com | kev...@berkeley.edu | PGP: 0xC22E1090 signature.asc Description: OpenPGP digital signature ___ crossfire mailing list crossfire@metalforge.org http://mailman.metalforge.org/mailman/listinfo/crossfire
Re: [crossfire] Crossfire Client 1.72.0 is available
Just wanted to add my 2 cents and say that anything that makes the client more accessible on windows is a big plus to me. Even though i'm happy to set the game up on linux, most of my friends are not, by offering support to windows we can gain access to a larger player base. Regards, Saru On Tue, Aug 15, 2017 at 3:22 PM, BloodyShadewrote: > On 8/15/2017 2:00 AM, Ruben Safir wrote: > >> On 08/14/2017 05:39 PM, Kevin Zheng wrote: >> >>> . If you play, >>> but use a package from your OS, I don't see how this impacts you. >>> >> >> I compile it >> >> and I don't think there is a package. I hate cmakes license, and I'm >> not found of its syntax either. >> >> I'm just generally sick of BSD junk being forced on me, and FWIW, if it >> never compiles on Windows, that is fine as well. >> >> >> >> > So you'd rather make it both harder to maintain and less platform > independent for others just because of your ideological standpoint in > regards to licenses and some minor inconvenience of installing a few more > packages? > > Also, as Kevin said, you can keep using the old system and adapt it to > your own needs, nobody is forcing anything on anybody here. > > Back when I used to play, I had to change things in the source and > basically rewrite the msvc project completely to be able to compile it on > windows xp/7 at the time. > Kevin might even remotely remember me, since I reported many ansi c (and > other) issues, which I found during that time. > > In short, making the source more platform independent and easier to > maintain for the current maintainers sound like a good step forward to me. > > Regards, > BloodyShade > > ___ > 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] Crossfire Client 1.72.0 is available
On 8/15/2017 2:00 AM, Ruben Safir wrote: On 08/14/2017 05:39 PM, Kevin Zheng wrote: . If you play, but use a package from your OS, I don't see how this impacts you. I compile it and I don't think there is a package. I hate cmakes license, and I'm not found of its syntax either. I'm just generally sick of BSD junk being forced on me, and FWIW, if it never compiles on Windows, that is fine as well. So you'd rather make it both harder to maintain and less platform independent for others just because of your ideological standpoint in regards to licenses and some minor inconvenience of installing a few more packages? Also, as Kevin said, you can keep using the old system and adapt it to your own needs, nobody is forcing anything on anybody here. Back when I used to play, I had to change things in the source and basically rewrite the msvc project completely to be able to compile it on windows xp/7 at the time. Kevin might even remotely remember me, since I reported many ansi c (and other) issues, which I found during that time. In short, making the source more platform independent and easier to maintain for the current maintainers sound like a good step forward to me. Regards, BloodyShade ___ crossfire mailing list crossfire@metalforge.org http://mailman.metalforge.org/mailman/listinfo/crossfire
Re: [crossfire] Crossfire Client 1.72.0 is available
On 08/14/2017 06:09 PM, Matthew Giassa wrote: > If you have strong opinions you should have voiced them in May 2014 when > CMake supported landed. It was clandestiningly been used before that, FWIW, and the autoconf config had been broken for quite a while. It so happened that in 2014 I was a little busy working on my artificial intelligence project and helping out with my grandchildren in Israel so I guess I missed the memo. Clearly it didn't land at that time. At one time it would only compile with imake. Its been a long time since ./config make make install worked cleanly. In the end, it only matters what the person doing the coding wants, but I would just point out that the autoconf has been dysfunctional for a long time and code base has been moved about different config systems a number of times and yes it does matter to me what license the build system is under. I would prefer strongly that the whole thing was locked up air tight in GPL3 -- So many immigrant groups have swept through our town that Brooklyn, like Atlantis, reaches mythological proportions in the mind of the world - RI Safir 1998 http://www.mrbrklyn.com DRM is THEFT - We are the STAKEHOLDERS - RI Safir 2002 http://www.nylxs.com - Leadership Development in Free Software http://www2.mrbrklyn.com/resources - Unpublished Archive http://www.coinhangout.com - coins! http://www.brooklyn-living.com Being so tracked is for FARM ANIMALS and and extermination camps, but incompatible with living as a free human being. -RI Safir 2013 ___ crossfire mailing list crossfire@metalforge.org http://mailman.metalforge.org/mailman/listinfo/crossfire
Re: [crossfire] Crossfire Client 1.72.0 is available
On 08/14/2017 05:39 PM, Kevin Zheng wrote: > . If you play, > but use a package from your OS, I don't see how this impacts you. I compile it and I don't think there is a package. I hate cmakes license, and I'm not found of its syntax either. I'm just generally sick of BSD junk being forced on me, and FWIW, if it never compiles on Windows, that is fine as well. -- So many immigrant groups have swept through our town that Brooklyn, like Atlantis, reaches mythological proportions in the mind of the world - RI Safir 1998 http://www.mrbrklyn.com DRM is THEFT - We are the STAKEHOLDERS - RI Safir 2002 http://www.nylxs.com - Leadership Development in Free Software http://www2.mrbrklyn.com/resources - Unpublished Archive http://www.coinhangout.com - coins! http://www.brooklyn-living.com Being so tracked is for FARM ANIMALS and and extermination camps, but incompatible with living as a free human being. -RI Safir 2013 ___ crossfire mailing list crossfire@metalforge.org http://mailman.metalforge.org/mailman/listinfo/crossfire
Re: [crossfire] Crossfire Client 1.72.0 is available
Nope, no strong opinions. Just curious. Original Message From: Kevin Zheng Sent: Monday, August 14, 2017 2:40 PM To: crossfire@metalforge.org Reply To: Crossfire Discussion Mailing List Subject: Re: [crossfire] Crossfire Client 1.72.0 is available On 08/14/2017 08:16, Matthew Giassa wrote: > Seconded. Why overhaul the build tool chain in use? What gain is there? The original reasons were better support for parallel builds, out of source builds, and Windows builds. Yes, Autotools technically supports all of these features. But the CMake build files are a lot shorter than the Autotools ones. At one point we had both build systems co-existing, but Autotools started lagging and breaking. Since nobody was willing to maintain it it got axed. We're happy to resurrect it if you step up as maintainer. If you have strong opinions you should have voiced them in May 2014 when CMake supported landed. If you don't even play I don't see how this impacts you. If you play, but use a package from your OS, I don't see how this impacts you. If you really want to use autotools you can keep using an older version of the client, so I don't see how this impacts you. Cheers, Kevin -- Kevin Zheng kevinz5...@gmail.com | kev...@berkeley.edu | PGP: 0xC22E1090 ___ 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] Crossfire Client 1.72.0 is available
On 08/14/2017 08:16, Matthew Giassa wrote: > Seconded. Why overhaul the build tool chain in use? What gain is there? The original reasons were better support for parallel builds, out of source builds, and Windows builds. Yes, Autotools technically supports all of these features. But the CMake build files are a lot shorter than the Autotools ones. At one point we had both build systems co-existing, but Autotools started lagging and breaking. Since nobody was willing to maintain it it got axed. We're happy to resurrect it if you step up as maintainer. If you have strong opinions you should have voiced them in May 2014 when CMake supported landed. If you don't even play I don't see how this impacts you. If you play, but use a package from your OS, I don't see how this impacts you. If you really want to use autotools you can keep using an older version of the client, so I don't see how this impacts you. Cheers, Kevin -- Kevin Zheng kevinz5...@gmail.com | kev...@berkeley.edu | PGP: 0xC22E1090 ___ crossfire mailing list crossfire@metalforge.org http://mailman.metalforge.org/mailman/listinfo/crossfire
Re: [crossfire] Crossfire Client 1.72.0 is available
Seconded. Why overhaul the build tool chain in use? What gain is there? Original Message From: Ruben Safir Sent: Monday, August 14, 2017 8:07 AM To: Crossfire Discussion Mailing List Reply To: Crossfire Discussion Mailing List Subject: Re: [crossfire] Crossfire Client 1.72.0 is available > - Replace autoconf/automake build system with CMake why? Why do I need to add an entire new compiler set up. This has been tossed back and forth previously as well causing a creep of compile problems. autoconf is free software and it works. ___ 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] Crossfire Client 1.72.0 is available
If it also checks in ~/.crossfire/ so that old configs are picked up, it shouldn't be a problem. If it finds something in the old location, it should use that, but if it has to create a directory, I don't mind if it puts it under ~/.config/crossfire/. On 08/14/17 11:03, Ruben Safir wrote: the new location. For Unix-like systems, the new location is *~/.config/crossfire*. This is a drag and moving my keys around is why I stopped playing the last time. Things should have remained under ./.crossfire ___ crossfire mailing list crossfire@metalforge.org http://mailman.metalforge.org/mailman/listinfo/crossfire
Re: [crossfire] Crossfire Client 1.72.0 is available
> the new location. For Unix-like systems, the new location is > *~/.config/crossfire*. This is a drag and moving my keys around is why I stopped playing the last time. Things should have remained under ./.crossfire -- So many immigrant groups have swept through our town that Brooklyn, like Atlantis, reaches mythological proportions in the mind of the world - RI Safir 1998 http://www.mrbrklyn.com DRM is THEFT - We are the STAKEHOLDERS - RI Safir 2002 http://www.nylxs.com - Leadership Development in Free Software http://www2.mrbrklyn.com/resources - Unpublished Archive http://www.coinhangout.com - coins! http://www.brooklyn-living.com Being so tracked is for FARM ANIMALS and and extermination camps, but incompatible with living as a free human being. -RI Safir 2013 ___ crossfire mailing list crossfire@metalforge.org http://mailman.metalforge.org/mailman/listinfo/crossfire