This is an automated archive made by the Lemmit Bot.

The original was posted on /r/feedthebeast by /u/Munchalotl on 2024-10-21 14:23:20+00:00.

Hi, aspiring pack dev here. As I work to gradually polish the modpack project I’ve been working on, I feel like I’m perhaps straying a bit off course and focusing on smaller things that I shouldn’t be worried about given then early state of the pack. (For context: Pack is about foraging and exploring for cooking ingredients with a blend of casual/slice of life/roleplay elements and “epic quest” vibes.) For instance, instead of seeking out conflicting recipes I’m making new recipes using modded items to make mods communicate with each other – on one hand, it allows for more interplay, but on the other hand there are more important issues to tackle.

This has been a solo project thus far, outside of my handful of playtesters. As such, the project is only really getting my eyes on it on the development side of things – and while I’ve played a few modpacks, my exposure is limited, and I’ve never made a pack either.

As I mentioned earlier, I know of a few things I need to shift my focus away from/toward. But I’d still like to be made aware of my potential blind spots, given that I’m a newbie to all of this. What is it that you feel makes a pack work for you? What turns you off of a pack hard? What makes you think “oh this is unpolished” versus “oh this has some nice effort put into it?” What are necessities in a larger pack for you? What kind of mod interactions make or break the experience for you?