You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reasons why I think this game would be a good addition to the WhyNot? game
More storage options are never a bad thing :)
1. In what ways might this mod take over the game?
It can't.
2. When could this mod be a strain on the server when no players are using the mod?
Shouldn't be any more strenuous than regular chests.
3. When does this mod destroy player's work?
It can't.
4. Have you looked at the code? If so, what stood out as things that might need fixing?
todo
5. In what way might this mod be reduced to be more simple (as in "Keep it Simple Stupid") (ex: "the foobar mod could be made more simple by splitting into two mods, foo and bar")
todo
6. Is this mod survival friendly? What items that it provides that should be craftable/obtainable, but arent?
Yes. None.
7. When does this mod feel like cheating?
I don't think it does. It's not an infinite chest...
8. Does this mod use the software "git" for version control? (note: we are asking about git. Github, Gitlab, notabug and hundreds of other git providers exist but are not specificly needed, although these do qualify).
Yes. See above.
9. Upon testing this mod, what errors, odd behavior, or other incompatibilities were noticed?
todo
10. Is the licence one that we can include in WhyNot? (Whynot is under the GPLv3 only. Be sure you know what you are talking about or cite your source)
Some chest code copied from MTG's default. Other code is MIT which is compatible with GPLv3.
The text was updated successfully, but these errors were encountered:
URL for mod to be added
https://github.com/HybridDog/connected_chests
Reasons why I think this game would be a good addition to the WhyNot? game
More storage options are never a bad thing :)
1. In what ways might this mod take over the game?
It can't.
2. When could this mod be a strain on the server when no players are using the mod?
Shouldn't be any more strenuous than regular chests.
3. When does this mod destroy player's work?
It can't.
4. Have you looked at the code? If so, what stood out as things that might need fixing?
todo
5. In what way might this mod be reduced to be more simple (as in "Keep it Simple Stupid") (ex: "the foobar mod could be made more simple by splitting into two mods, foo and bar")
todo
6. Is this mod survival friendly? What items that it provides that should be craftable/obtainable, but arent?
Yes. None.
7. When does this mod feel like cheating?
I don't think it does. It's not an infinite chest...
8. Does this mod use the software "git" for version control? (note: we are asking about git. Github, Gitlab, notabug and hundreds of other git providers exist but are not specificly needed, although these do qualify).
Yes. See above.
9. Upon testing this mod, what errors, odd behavior, or other incompatibilities were noticed?
todo
10. Is the licence one that we can include in WhyNot? (Whynot is under the GPLv3 only. Be sure you know what you are talking about or cite your source)
Some chest code copied from MTG's default. Other code is MIT which is compatible with GPLv3.
The text was updated successfully, but these errors were encountered: