Add support for plugins and resource packs

emma commented

2022-08-28 04:48:11 +00:00

Owner

It would be great to be able to manage and update plugins and resource packs in addition to mods with hopper, and we should also consider updating from other sources if possible.

[More information](https://blog.modrinth.com/plugins-resource-packs/) It would be great to be able to manage and update plugins and resource packs in addition to mods with hopper, and we should also consider updating from other sources if possible.

emma added the

enhancement

label 2022-08-28 04:48:11 +00:00

spookdot was assigned by emma

2022-08-28 06:39:14 +00:00

spookdot commented

2022-08-29 09:55:09 +00:00

Member

I can likely make add other sources. But this does leave the question how we would best design the CLI for this

Right now we usually write hopper get <searchTerm>

If we are going to differentiate between mods, plugins and resource packs it would be good to either allow a filter flag or to separate them entirely

So either hopper get <searchTerm> --mod, hopper get mod <searchTerm>, hopper get-mod <searchTerm> or hopper mod get <searchTerm>

I'd personally tend towards either a filter flag or something along the lines of get-mod, so people have all three options displayed in the main help command and don't have to look up the help command for the get subcommand

I can likely make add other sources. But this does leave the question how we would best design the CLI for this Right now we usually write `hopper get <searchTerm>` If we are going to differentiate between mods, plugins and resource packs it would be good to either allow a filter flag or to separate them entirely So either `hopper get <searchTerm> --mod`, `hopper get mod <searchTerm>`, `hopper get-mod <searchTerm>` or `hopper mod get <searchTerm>` I'd personally tend towards either a filter flag or something along the lines of get-mod, so people have all three options displayed in the main help command and don't have to look up the help command for the get subcommand

emma commented

2022-09-06 22:53:29 +00:00

Author

Owner

For posterity:

get [OPTIONS] PACKAGE

 Searches for a PACKAGE, displays the results, and downloads any selected PACKAGES to the local cache.

OPTIONS

 -n, --no-confirm

  Does not display search results and downloads exact matches to the cache. Requires --mc-version and --type be specified.

The hopper get command should search all types of packages for the search term, only searching specifically if --mc-version and/or --type is specified.

For posterity: ``` get [OPTIONS] PACKAGE Searches for a PACKAGE, displays the results, and downloads any selected PACKAGES to the local cache. OPTIONS -n, --no-confirm Does not display search results and downloads exact matches to the cache. Requires --mc-version and --type be specified. ``` The `hopper get` command should search all types of packages for the search term, only searching specifically if `--mc-version` and/or `--type` is specified.

emma commented

2022-09-06 22:55:41 +00:00

Author

Owner

The types should be fabric, forge, quilt, resource (resource pack), and pack (modpack).

The types should be `fabric`, `forge`, `quilt`, `resource` (resource pack), and `pack` (modpack).

spookdot commented

2022-09-11 19:11:01 +00:00

Member

What about plugins?

emma commented

2022-09-12 01:45:50 +00:00

Author

Owner

What about plugins?

oh. yea. plugin. oops lmao

> What about plugins? oh. yea. `plugin`. oops lmao

spookdot commented

2022-09-13 21:16:57 +00:00

Member

Shouldn't we maybe differentiate between different plugin options? Like paper, purpur, Spigot and what not there are out now? Also maybe we should have options for fabric modpacks, forge modpacks and if there ever are any quilt modpacks?

emma commented

2022-09-13 21:47:39 +00:00

Author

Owner

Shouldn't we maybe differentiate between different plugin options? Like paper, purpur, Spigot and what not there are out now? Also maybe we should have options for fabric modpacks, forge modpacks and if there ever are any quilt modpacks?

good point. probably should be $loader-pack and $loader-plugin, what do you think?

> Shouldn't we maybe differentiate between different plugin options? Like paper, purpur, Spigot and what not there are out now? Also maybe we should have options for fabric modpacks, forge modpacks and if there ever are any quilt modpacks? good point. probably should be `$loader-pack` and `$loader-plugin`, what do you think?

spookdot commented

2022-09-13 21:48:29 +00:00

Member

I agree. Also keeps it a bit more clearer on the difference between modpack and resourcepack, since we're using resource for resourcepacks

I agree. Also keeps it a bit more clearer on the difference between modpack and resourcepack, since we're using `resource` for resourcepacks

👍 1

spookdot referenced this issue

2022-09-16 16:55:33 +00:00

Add support for filtering plugins and resource packs #14

emma commented

2022-11-17 20:33:09 +00:00

Author