Hello dev,

It appears I've ran into a problem with your mod and it mentioned your mod was the issue after reading a nemesis book.

Minecraft: 1.12,2
Forge: 14.23.5.2768
torotraits: 1.12-1
nemesissystem: 1.12.1-2

Crash Report: https://paste.dimdev.org/yubareyoce.mccrash

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

Hey @DatrixTHLK, thanks for the feedback. It's good to hear that you've enjoyed the mod so much, and it's compelling to read your passionate thoughts. I cannot guarantee that we will or will not resume development on this or any mod, since they are all just a fun hobby we do in our spare time. Spare time being limited, we appreciate your continued support, understanding, and time as we squeeze in changes and new development here and there across all of our mods.

We don't make calls on how to spend our time based solely on the popularity of a mod. We come up with ideas when we're hanging out together talking about games, Minecraft, and our lives. The few that get made are the ones that we want to play with ourselves. I know it sucks to see one you like fall by the wayside. Each of us in ToroCraft itself have favorites, and I certainly wish I had more time to spend working on all of them. When we decide how to spend the small amount of hobby development time that we have, we balance our own desires with the desires of those using our mods.

In general, the most used mods must be given priority, because problems there impact the most people. That said, we hear you, and your comments hold significant weight and meaning. For me personally, it's an enjoyable reminder that some folks really enjoy our work.

Take care,
Paul

First off let me say that I've enjoyed this mod, very much so. I've noticed you've said that this mod never really caught, which I'm guessing means you were hoping this mod would be a lot more popular. I'd like to point out that if this is how you guys thought, then that will set you up for failure (I'm not assuming you did think this way). Just make the mod because it's fun or it's a hobby you do in your spare time. This is how I do it when I made websites. I do it not because everyone will like it, I do so because, I will like it and it's my hobby and a job.

There are a whole lot of mods that aren't very popular compared to the ones that have a million downloads and yet they are still being worked on for the small amount of folks who enjoy it. I like the mods that don't have many downloads because it gives me a fresh look at how mods look, act and feel within the game and how they interact with one another.

I don't know if you guys will ever come back to this or if someone can pick it up and work on it...
Anyways a new crash issue has come up similar to my first post above, but different in a way
Crash Log: https://paste.dimdev.org/umohufujad.mccrash

I know nothing will be done about this at this point in time, but I am hopeful and I'm really patient in most cases.

In closing don't take this as me bashing this mod in any way. I'm just from the opinion that popularity isn't everything. I hope one day you guys or someone will come and pick this up.

If I may quote your GitHub home page: "This mod is still in early development
If you have any thoughts or problems with the mod, please let us know."

I'd really hate to get rid of your mod out of my mod list, but I'm going to have to if nothing is to be done about this.

If you have somewhere else we can get these issues to you and respond to faster let me know. Now I usually can wait as long as it takes for some mod maker/developer to respond to the issue at hand (that could take as long as 6 days to 6 months or even a year so I'm extremely patient), but not when a bot is in place to mark each issue as stale when the issuer feels legitimately about their issues/enhancements. This also doesn't mean that you should rush to respond to me either. Take your time, I'm patient.