Sunday Proposal Guidelines
Ideal proposals should be defined as clear deliverables. Describing changes in qualitative means requires me to research, interpret, and engineer your creative ideas into actionable code/configs. This process takes time and effort on my part which, on a reoccurring basis, it simply not sustainable. As such, I have written the following guidelines for Sunday proposals moving forward:
Good Proposals
- Changing a single config found at Pokejong.com/configs
- Adding a single [SERVER SIDE, Fabric, 1.21.1] mod or datapack from Modrinth.com
- Modifying a drop table for a single Pokemon (proposal should be formatted like this)
- Running a single, clearly defined command (eg
/chunky border add...
)
Grey Area Proposals
- Proposing a reoccurring (timed) server command
- Adding a mod from that requires significant configuration and discussion
Invalid Proposals
- Adding a mod with any client side component (this would require every user to re-download the modpack, which is a huge inconvenience to the player base)
- Proposing a general outcome (do not propose the end, propose the means)
- Proposing a feature qualitatively (be concrete in terms of mod, config, or command)
- Changing Server Hours to be online from 11am-4pm (this is when i do server maintenance)
- Requesting a novel feature to any of the custom mods I forked/created for the server (list can be found here) -- Coding an idea I want is fun, coding an idea someone else wants is work (software contracting). That being said, if you want to hire me to make Minecraft mod shoot me a message here