FOSS gamedev and creative worlds

removed

-1 for this method.
It makes the repo look ugly. Renaming the folder is not hard work, IMO.

There should be a little hint in "How to install mods" in the Mod release section for that.

PilzAdam wrote:There should be a little hint in "How to install mods" in the Mod release section for that.

There is.

8)

Calinou wrote:

PilzAdam wrote:There should be a little hint in "How to install mods" in the Mod release section for that.

There is.

8)

I mean in this post should be: "When downloading from GitHub rename the folder to what the mod is called in the [] at the end of the forum topic name."

how hard would it be to change the c++ to allow dashes in the filename? that would solve the issue at a core level.

cornernote wrote:how hard would it be to change the c++ to allow dashes in the filename? that would solve the issue at a core level.

Not realy. The items have to use the modname as a prefix.

It isn't even the dashes that's the problem - the problem is that the game requires the folder name to exactly match the name of the mod. Frankly, it would have been more than enough to issue a warning to the user, and then only in the console, because it's just as irritating to someone who knows what they're doing as to a new user who doesn't even know how to dig a block of dirt yet (sorry c55, the folder name issue was not one of your better decisions).

VanessaE, whats your opinion on the folder format recommendation for Git repos ?

Well, like you said, too many users out there have the problem you've described, though to be perfectly blunt it's because they don't bother to read and understand how to install mods in the first place, even when the mod in question includes some simple install instructions.

In lieu of a better idea, adding modpack.txt seems like the best solution - but some way to detect multiple copies of a given mod is needed in the near future (say due to having two or more versions of a mod with different foldernames due to different git commit hashes).

The easiest solution is the best:
create a folder with the correct name and files within ...

most people use this organization in Git:

textures
   | _ Texture1.png
   | _ Texture2.png
   | _ Other_textures.png

init.lua
Other. Lua
README.txt

I use:

mod_folder
   | _ Textures
   | | _ Texture1.png
   | | _ Texture2.png
   | | _ More_textures.png
   |
   | _ Init.lua
   | _ Other. Lua

README.txt

Tonyka, my mod repos are like this.

Tonyka, simply add a modpack.txt to the top level folder, then the whole thing can be unzipped directly from git to mods folder.