
Request that AlexsMobs Crocodile be added to list of mob spawn prevention in No Hostiles Around Campfire
warrentode opened this issue ยท 1 comments
Information
Minecraft version: 1.19.2+
Modloader: Forge / Fabric
Mod name: No Hostiles Around Campfire
Feature description
In AlexsMobs, the Crocodile is registered as CREATURE, not MONSTER, and this entity's AI targets all other mobs that aren't a Creeper. So this means they frequently drag villagers into the nearby river. By default they have a pretty high spawn rate, which is perfectly fine for out in the wild but not so much when trying to manage a village inside or near a river biome. Adding this mob to your mod's list of prevented spawns would easily and quickly address this. As player, I don't mind fighting for my life out in the wild, but I don't particularly care having a mob that attacks everything spawning in broad daylight inside my base.
I've only started using AlexsMobs, so I don't know if there are other entities in it that present a similar issue. All I know is that this is the one I keep running into and I've been using your mod for a long time now for protecting my bases. So if it's possible to add the crocodile to your list that would be seriously awesome.
Hey!
I appreciate the suggestion! While I'd love to add all features submitted on the issue-tracker, I've got to prioritize working on them due to having limited time. In order to see which features users would like to see most, I've created https://serilum.com/mods/requests, which shows a table with all feature request submitted.
I'm aware that this is not the reaction you were looking for, but the reality is that I can't keep up with the demand. I try to do as much as I can.
Users are able to upvote requests by reacting to the first issue comment on this GitHub page with one of the ๐ ๐ ๐ โค๏ธ ๐ ๐ emoji's. The request with the most unique reactions, will be shown at the top. You can of course add the reactions yourself too, but don't have to :). The author of the feature is already counted as +1.
I won't only focus on popular features in the upcoming years, but it does help with prioritizing. I'll probably work on a combination of popular and interesting/needed/fun submissions.
I'll close this issue with "not planned" as a way to separate an open feature request from an actual completed issue. This does not actually mean it's not planned! Incompatibilities and bug reports will still remain open.
When the feature is implemented, I'll again post a comment and close it as "completed".
Thank you for taking the time to submit the suggestion! โค๏ธ