To add to the drawbacks you mentioned (which are already quite some serious drawbacks). I think it will be quite some work to get a list working of all the resourcepacks from which a person can select one (as in, difficult to code and resource expensive). In my opinion too much work just to notify the creator of the pack.
Thereby, packs can update. A project might use an older version of a pack that is no longer available but the project creator doesn't update the map / remove the linked pack. Which can cause some confusing.
If it's possible to get this all solved and working it would be a really nice feature though.
Texture/Resource-pack linker on projects
“Member X makes a pack called Y.”
“Member N makes a project with pack Y in use.”
In the current situation Member X doesn't know that member N used his/her pack in a project without:
- Searching of his/her own on tags – if applied by member N – corresponding to pack Y;
- Getting a notification by member N;
- Getting a notification of member @.
What if you could add the pack click-able in use under the optional tab in “update/post project page”?
I mean this in a similar way you can search for fellow members for sending a pm, but
for packs.
With this more rigorous approach to linking a pack to a project the following benefits could be reached:
- The creator of the pack can easily – notified – keep track of projects made with his/her pack;
- The creator can get more satisfaction or pride out of it, as smaller packs are seldom
seen in the project section (my opinion);
- The creator can see more easily were the pack needs polishing due to different
compositions made by members than the pack previewer the creator used;
- The project maker(s) can easily find more reference project of the pack in use.
This can be useful for up-coming projects by getting new block combination ideas/
- A project viewer can easily find the pack as not everyone uses click-able links or
reference lacks at all;
- Potential pack users can easily see more reference projects before deciding to use a
pack – not all projects use only shaders or renders.
- Make automatic a reference collection of projects to show on the pack page. So people
can get more easily a wider view of a pack capabilities or lackings
of the pack in question.
Although there a benefits, there could be some drawbacks such as:
- Older projects are not – or near impossible – automatic linkable to packs;
- Misusing this feature to get in a way more attention, resulting in more work for
the moderators;
- Mistaking in the right pack as a lot of “simple” packs tend to use the same name;
- Mixed packs by members or rather different packs in use in the pictures → default,
pack Y & pack U.
Feel free to comment your opinion about this quickly written piece of ticket, before I
lost motivation once again to write it up.