Compose and document a way how we accept/unaccept features #1537
Labels
No Label
#P1 CRITICAL
#P2: HIGH
#P3: elevated
#P4 priority: medium
#P6: low
#Review
annoying
API
bug
code quality
combat
commands
compatibility
configurability
contribution inside
controls
core feature
creative mode
delayed for engine release
documentation
duplicate
enhancement
environment
feature request
gameplay
graphics
ground content conflict
GUI/HUD
help wanted
incomplete feature
invalid / won't fix
items
looking for contributor
mapgen
meta
mineclone2+
Minecraft >= 1.13
Minecraft >= 1.17
missing feature
mobile
mobs
mod support
model needed
multiplayer
Needs adoption
needs discussion
needs engine change
needs more information
needs research
nodes
non-mob entities
performance
player
possible close
redstone
release notes
schematics
Skyblock
sounds
Testing / Retest
tools
translation
unconfirmed
mcl5
mcla
Media missing
No Milestone
No project
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: VoxeLibre/VoxeLibre#1537
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I'm very sorry for bothering you with organizational tasks.
Moreover, the tasks which have no clear solution for me.
This is super low priority (developing process and fixes are currently much more important).
I just know, it's very important for MCL2 future, so let me articulate some blank and I'll appreciate if we polish it to some transitional (not final, just enough to take into the work) decision:
We accept:
We reject:
Okay, but then I shall reopen it for 'mineclone5' branch...
Ok
Compose and document a way how we accept/unaccept featuresto Compose and document a way how we accept/unaccept features for 'mineclone5' branchList of mentioned features of Minecraft, can't stop reading https://minecraft.fandom.com/wiki/Java_Edition_mentioned_features
I think we need to find a way to discuss features like a list, with possibility to upvote/downvote every feature. Just move up/down, like answers in stackoverflow :)
I'm renaming this issue back, because it's open question for me.
Compose and document a way how we accept/unaccept features for 'mineclone5' branchto Compose and document a way how we accept/unaccept featuresErr, if its open for the mineclone5 branch, and MineClone5 is now a game of its own, can this be closed yet?
Old meta issue that may be worth closing.