FOSS gamedev and creative worlds

Hi

I dont know if it was mention before but how about

Choosing mapgen dictly in settings instead of showing them in mods section.

instead of
V5
V6
V7
singlenode


this
v5
v6
v7
singlenode
ethereal
amgt
valeys_mapgen
...
...

This would require some way for mods to tell the engine that they are mapgen mods, without being loaded.
This would be cool, but would require some engine changes to be done.

A minor code addition to indicate the correct path to check for mapgen mods - which then puts the responsibility of installing mapgen mods in the correct folder back to the user.

Maybe seperate folder for Mapgen mods ? And then the settings menu can read it from there

But then what about games or modpacks that depend on a specific mapgen? Would we have to distribute the mapgen mods separately from the game/modpack to be able to use it?

In my opinion, the window popup that is shown when creating a new world for a game should be game-specific and moddable. For many games it makes no sense to be able to select the mapgen because it'll get overriden from Lua (and if it was included as a mod like this, it would most likely cause conflicts if you choose the wrong one). Instead there could be custom options from the particular game you are creating the world for.

+1,
Good idea

Nah.

Ferk wrote:But then what about games or modpacks that depend on a specific mapgen? Would we have to distribute the mapgen mods separately from the game/modpack to be able to use it?

In my opinion, the window popup that is shown when creating a new world for a game should be game-specific and moddable. For many games it makes no sense to be able to select the mapgen because it'll get overriden from Lua (and if it was included as a mod like this, it would most likely cause conflicts if you choose the wrong one). Instead there could be custom options from the particular game you are creating the world for.

You dont have to distribute mapgen seperatly from games.You can still include as a mod in its folder.
For games which needs spesific mapgen can force the mapgen to choose.
And there could be a new feature as blacklisted mods.For exp if a game or mod is not compatible some mapgens/mods it wont allow you to choose it.

mahmutelmas06 wrote:And there could be a new feature as blacklisted mods.For exp if a game or mod is not compatible some mapgens/mods it wont allow you to choose it.

This pull allows specifying mod conflicts.

maybe add a new way to add mg by puting them in the engine ?

it's a nice idea, but many people of here is ok with the actual mapgens!

MineYoshi wrote:it's a nice idea, but many people of here is ok with the actual mapgens!

...this change wouldn't get rid of "actual mapgens"

rubenwardy wrote:

MineYoshi wrote:it's a nice idea, but many people of here is ok with the actual mapgens!

...this change wouldn't get rid of "actual mapgens"

I mean, the actual mapgens are ok!

I don't think we need so much add ethereal or others...

But if you want then do it!

MineYoshi wrote:

rubenwardy wrote:...this change wouldn't get rid of "actual mapgens"

I mean, the actual mapgens are ok!

I don't think we need so much add ethereal or others...

But if you want then do it!

You misunderstand, they're not talking about including them by default.
What they want is when you have Lua mapgens installed, for them to appear in the mapgen list.

rubenwardy wrote:

MineYoshi wrote:

rubenwardy wrote:...this change wouldn't get rid of "actual mapgens"

I mean, the actual mapgens are ok!

I don't think we need so much add ethereal or others...

But if you want then do it!

You misunderstand, they're not talking about including them by default.
What they want is when you have Lua mapgens installed, for them to appear in the mapgen list.

i understand it, i only think isn't so necessary, the actual mapgens are ok for many people here.

But as i said before i don't think is so necessary!