Ah, I suppose I should say new hexemelio.tilespec FROM v2.6.00.cazfi wrote:It's part of freeciv proper. (That's why hexemplio was created in the first place - to have tileset like amplio2hexbig but with such a filesize that it's feasible to include in freeciv distribution).GriffonSpade wrote:new hexemplio.tilespec for v2.6.00.
AmplioHexBig 2.6
- GriffonSpade
- Elite
- Posts: 578
- Joined: Mon Apr 29, 2013 4:41 pm
Re: AmplioHexBig 2.6
Re: AmplioHexBig 2.6
Latest (as this URL does not specify revision number) S2_6 data can be seen from: http://svn.gna.org/viewcvs/freeciv/branches/S2_6/data/GriffonSpade wrote:Ah, I suppose I should say new hexemelio.tilespec FROM v2.6.00.
Re: AmplioHexBig 2.6
For one ruleset I would need "Path" as separate road type, to be built before paved "Road" we already have in most rulesets.
Re: AmplioHexBig 2.6
I see you now release many files under Creative Commons that is not compatible with GPL, and thus makes it impossible for us to use those particular files in freeciv proper.
Re: AmplioHexBig 2.6
Some files use format like "x, y, tag1, tag2, tag3". That doesn't work (I've seen some people to try to use it in the past). There is just one "tag" column, later ones will be ignored.
Re: AmplioHexBig 2.6
CC0 is public domain, no problem. CC BY 4.0 is also okay, CC BY SA 4.0 in the next paragraph is under discussion (FSF + CC).cazfi wrote:I see you now release many files under Creative Commons that is not compatible with GPL, and thus makes it impossible for us to use those particular files in freeciv proper.
- GriffonSpade
- Elite
- Posts: 578
- Joined: Mon Apr 29, 2013 4:41 pm
Re: AmplioHexBig 2.6
I think I've finally figured out what you meant. You mean like this?cazfi wrote:Some files use format like "x, y, tag1, tag2, tag3". That doesn't work (I've seen some people to try to use it in the past). There is just one "tag" column, later ones will be ignored.
Code: Select all
0, 1, "t.l0.plains1", ;[PA]
"t.l0.hills1", ;[PA]
"t.l0.mountains1" ;[PA]
And yes, I chose CC0 for my own work (that is to say, explicitly, solely by me) because it allows anyone to use it without reservation or restriction.
It's always frustrating to me when I find neat stuff that I can't use officially because of licensing issues, so I'd prefer if I don't do it to others.
Obviously, this does not apply to anything I do using others' work, where I maintain their license and do my best to maintain credits.
- GriffonSpade
- Elite
- Posts: 578
- Joined: Mon Apr 29, 2013 4:41 pm
Re: AmplioHexBig 2.6
Alright, after coming back after a couple months to thinking about how I'm going to set this up, I think I know how I'll do it. Most of me wanting to keep it completely separate is down to how I have my files stored.
First, I'll separate it into two parts:
The first part will be 'Hexemplio beta'. It will be files in the ampliohexbig directory as per usual, but only the ones that deviate from current hexemplio.
Then the second part will be 'AmplioHexBig'. It will be all the stuff that's currently XU/GT.
And now that I've written it out, I don't have to worry about forgetting about it.
Edit: And here's the hexemplio 2.6 beta patch. I just replaced everything in the hexemplio folder because so much was changed. Went through each spec file and compared/updated line by line to make sure everything was included (such as the bases notes). Note that even the spec files that didn't have any script changes usually had credit changes.
First, I'll separate it into two parts:
The first part will be 'Hexemplio beta'. It will be files in the ampliohexbig directory as per usual, but only the ones that deviate from current hexemplio.
Then the second part will be 'AmplioHexBig'. It will be all the stuff that's currently XU/GT.
And now that I've written it out, I don't have to worry about forgetting about it.
Edit: And here's the hexemplio 2.6 beta patch. I just replaced everything in the hexemplio folder because so much was changed. Went through each spec file and compared/updated line by line to make sure everything was included (such as the bases notes). Note that even the spec files that didn't have any script changes usually had credit changes.
Re: AmplioHexBig 2.6
I'm struggling with irrigation (and farmland) stuff. Why is extrastyle of those changed from "Cardinals" to "River"? Do they have delta to ocean like rivers do?
- GriffonSpade
- Elite
- Posts: 578
- Joined: Mon Apr 29, 2013 4:41 pm
Re: AmplioHexBig 2.6
Yeah, they use the river mouths to appear properly connected to water sources. Having that beach between the irrigation and its source looked very off, and I don't have to rely on the half-assed version with little squiggly blue lines drawn outside the border.cazfi wrote:I'm struggling with irrigation (and farmland) stuff. Why is extrastyle of those changed from "Cardinals" to "River"? Do they have delta to ocean like rivers do?
Edit:
Could you elaborate on this? The standard brown road would be considered 'paved' (or at least a proper Roman road), and you need a smaller, thinner one to represent narrow paths through the wilderness?For one ruleset I would need "Path" as separate road type, to be built before paved "Road" we already have in most rulesets.