Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

This repo's stance on hosting plugins and mods #26

Open
DeerTears opened this issue Dec 24, 2021 · 1 comment
Open

This repo's stance on hosting plugins and mods #26

DeerTears opened this issue Dec 24, 2021 · 1 comment
Labels
wontfix This will not be worked on

Comments

@DeerTears
Copy link
Owner

DeerTears commented Dec 24, 2021

The year is 2021, and 3.0 has just launched. Now we have a huge abundance of plugins entering the GB Studio dev sphere, as shown by this plugin database I've been keeping: https://docs.google.com/spreadsheets/d/1d2F5hSEMt6nkacw-qVnYlT3IPHqmCCaLFhRboC5xxc0/edit#gid=0

I think the rise of plugins/engine mods has been really awesome to see. Athough this repo is pretty popular in the community, and I love giving away resources to people, I feel like this repo is not the place to host plugins or mods at all. Here's why:

  1. Engine mods can be hundreds of megabytes. Adding these would massively bloat the .zip of the repo for people who download GBSCA as a quick way to get graphics and music for their games.
  2. Plugins and engine mods are incredibly version-specific, and we don't have a way to tag files quickly. Tags on commits are confusing, and I'm still actively considering ways to make it easier for non-git users to use these assets.
  3. I already went through the effort to make this spreadsheet https://docs.google.com/spreadsheets/d/1d2F5hSEMt6nkacw-qVnYlT3IPHqmCCaLFhRboC5xxc0/edit#gid=0 and each new entry only takes 20 seconds to add. Any significant PR to a public repo like this deserves more consideration and appreciation than just 20 seconds. <3
  4. This repo will never have every plugin because any of the above reasons will discourage people from submitting plugins, so unlike the spreadsheet, this repo can't be used as a complete list to find the exact plugin you want.

I hope this has been convincing enough, I'm happy to hear objections or other alternatives that this repo could still promote/contribute to, but ultimately I don't think it's for this repo. There can always be other repos that aim to do this as well. You can create your own repository for public plugins, or even host a personal collection like NalaFala and Pautomas have (as seen by their prevalence in the spreadsheet).

Again, https://docs.google.com/spreadsheets/d/1d2F5hSEMt6nkacw-qVnYlT3IPHqmCCaLFhRboC5xxc0/edit#gid=0 this spreadsheet has just been too useful for me to quickly maintain, and I'd rather link to wherever you post your plugin in the spreadsheet rather than have it be added to the repo.

If you have a plugin you want added to the spreadsheet, you can comment with a link to it in this issue. This won't be as fast as if you just ping me on the GB Studio Discord though.

@mxashlynn
Copy link
Collaborator

I support all of this reasoning. 👍

@DeerTears DeerTears added the wontfix This will not be worked on label Jan 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

2 participants