Quote:
Oh please dont make me guilty of blowing you away. The other rmg appears to have stopped in development and you were on such a roll. But on the other hand I would be the last person to recommend that anyone not pursue the parts they feel are fun.
|
So far I'm still having fun with it, and I'd dare say I'm not at all far from getting it to a usable beta state.
It can currently generate maps, place provinces and draw borders. It still needs some improvement on the last two until they are correct. After that there's actually generating the .map files (which shouldn't be hard, as I already store information of all neighbours and the terrain bitmask.).
After that, all that's left is making everything customizable rather than having almost all values hard-coded, and making the maps look graphically prettier.
Then I can release version 1.00 and start improving it based on suggestions
Oh, and if you feel like blowing new wind into my sails, then you are doing so with your inclination to host some maps generated with this RMG on your site.
This is because I'm about to add a few things which will be quite computationally expensive
Quote:
Well it works for me anyway you want to do it. As for the colors.. Old Dom 1, and DomMap, both went with speckling the province with color. So one possible choice would be assigning a color to each basic terrain, and a setting for variation. Such as brown to mountain, and yellow to waste, then have the program speckle the two colors together for provinces which were mountain-waste. If the variation variable is set to 3 then the game could randomly use -3/+3 of the brown for each mountain pixel and -3/+3 of yellow for each waste. That would give a nicely blurred effect. Not so stark. And provide some effect provinces which are entirely mountain or entirely waste.
|
I saw it and I didn't really like it. I'm more inclined to have a single color per basic terrain and have the resulting color just be an average of all colors that apply (that's what it's like right now, except all values are hard-coded). The real variation should come by also assigning an image (or images) to each terrain type (like little mountains and trees) and have the program spread all applicable images on the terrain.
(Of course, there's always the option of providing more than one option
)
Quote:
I don't want to hijack another thread
|
I'm actually quite interested in what you have, since in a way you are a competitor
