minetest-whynot
/
whynot-game
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
633 Commits
1 Branch
0 Tags
46 MiB
Lua 94.6%
TypeScript 2.2%
Python 1.5%
HTML 1%
Shell 0.5%
Other 0.2%
 
 
 
 
 
 
Go to file
Olivier Dragon 775e687d7a
Merge pull request #131 from dacmot/use_minetest_mirrors_notabug 
Use minetest mirrors notabug
 		2022-09-03 11:52:02 -04:00
.github/ISSUE_TEMPLATE Make intent of empty bullet point clearer 2022-05-01 17:24:41 -06:00
builder Merge pull request #129 from minetest-whynot/buildscripts_compat 2022-09-01 17:43:30 -04:00
menu Game icon and header 2018-01-08 20:50:03 +01:00
mods Rsync cleanup for laptop 2022-08-31 22:35:45 -04:00
.gitattributes Revert "Add qa_block test results to track regressions" 2022-08-18 13:59:30 -04:00
.gitmodules Replace notabug repos with mirrors 2022-09-02 22:41:51 -04:00
README.md Whynot wording 2022-03-10 07:36:24 +01:00
game.conf Change conf name to title 2022-08-18 01:08:25 -04:00
minetest.conf added trash_can to the game 2019-08-16 19:25:55 +02:00
mod_sources.txt Update mod_sources.txt 2022-09-02 22:44:02 -04:00

README.md

whynot-game

A Game for MineTest in mod-collection style

This game shows the diversity of the MineTest community. The game does not follow any theme and does not try to clone any other blocky game, just minetest as known in community.

The name describes the way the mods are applied to the game. The game does not have rules for mods to be applied, all mods are welcome. But there are some rules why a mod cannot be applied to the game.

List of already included mods

Generated file: mod_sources.txt

License statement

Each of the mods do have their own free license. The whynot related work (such as the buiding scripts) are GPL-V3

Contribution

If you find bugs in mods - please report them directly to the upstream.

Whynot related issues, new mod suggestions or if the bugs cannot be solved by upstream, please open issue in repository https://github.com/minetest-whynot/whynot-game.

Whynot Rules for mods

1 don't take over the game

Unfortunately a lot of great mods assume the player likes to play with this mod only. This game stands for diversity. That means if a player does not like an included mod, they can play the game without using that mod (few exceptions).

2 don't take over the server

Thinking alongside point 1, the mod should be not strain the server if the mod is not in use. That means no unnecessary ABM's and so on.

3 don't destroy the world

The mod should not be able to destroy players' work.

4 no bad code quality

I look into the lua code of each mod before I make my decision. I am tolerant against imperfect code, but roughly negligent and/or bad code will be rejected. Advantage for the mod developer: They get a code review for free ;-) And if I like the mod, I might contribute some optimizations to get the mod ready for the game.

5 no all-in-one mods or lots of unused dependencies

It is difficult to consider an all-in-one mod for these described rules. Therefore an all-in-one mod might be rejected.

6 most items obtainable in survival

The game should be playable in survival. Therefore the items should be obtainable

7 No cheating mods

The mods should not feel like cheats. The tools should be worn, walking through the world and searching for rare items should not be made obsolete by item generators.

8 Mod under version control

This game is not a new home for mods. Each mod remains within and have their own upstream. Access by version control is required for scripted updates to the game. If bugs are found in mods in this game, please report them to the upstream sources.

9 Mod must not be incompatible with other mods

Mods should not require compatibility code to be added to the Whynot game, and thus requiring extra maintenance work on our part. If we find incompatibilities (ex. recipes conflicts, redundant items, keypress overlap) we expect any required changes to happen upstream before the mod is added to whynot. Some exceptions may be considered on a case-by-case basis.