The Vanilla Experience (Mod) (Forge)

The Vanilla Experience (Mod) (Forge)

118k Downloads

Dragon Drops Elytra: Add config support for specifying enchants

Wolfdv1 opened this issue ยท 1 comments

commented

Information

Minecraft version: 1.21.4 - Tho as is quite basic can be likely merged/back ported to all 1.21 versions that support the new data driven enchants
Modloader: Forge / NeoForge / Fabric / Quilt

Mod name: Dragon Drops Elytra

Feature description

I wanted to specify some enchants for the Elytra to have when dropped from the dragon.
For me I wanted to nerf it somewhat with Curse of Binding and Curse of Vanishing- this would allow it to be used but also give incentive for exploring to find the 'Vanilla' one in the end city.
I hard coded this for my own uses but decided might be nice to have this as a config driven option.

Will submit a PR shortly, apologies if I have missed an option in Collective.Config.DuskConfig for Array/Lists - just used some regex and basic string logic for this.

Thanks all for the good work, have a nice one.
commented

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! โค๏ธ