Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

[LM4b] To-do List #457

Closed
5 of 71 tasks
lokka30 opened this issue Jun 11, 2023 · 2 comments
Closed
5 of 71 tasks

[LM4b] To-do List #457

lokka30 opened this issue Jun 11, 2023 · 2 comments
Assignees
Labels
priority: normal Normal priority status: confirmed Confirmed by a maintainer status: in progress Work in progress type: improvement Add or adjust a feature
Milestone

Comments

@lokka30
Copy link
Member

lokka30 commented Jun 11, 2023

A new to-do list for yet another revision of LM4. 馃槃

  • It's listed in order of what should be done first, though the list is pretty flexible, so no need to follow it strictly.
  • This list is not definitive, it is being edited very frequently, tasks are constantly being added.
  • A checkmark indicates that a task is work-in-progress. Completed tasks are removed from the list entirely.
  • Assigness are merely a suggestion, anyone in the team can work on anything.
  • LM4 accepts contributions, let me know if there's something you'd like to work on. 馃檪

List

  • Reimplement API from LM4a (@lokka30)
    • so we can get started using PDC stuff. :)
  • Complete the EntityLabelLib project.
  • Implement various actions
    • Fundamental
      • exit-rule (@lokka30)
        • Terminates the current rule.
      • exit-rules (@lokka30)
        • If a rule running exit-rules has been called by another rule, then LM will recursively exit each rule's caller.
        • Exact same as exit-all from LM4a, just renamed.
      • call-rule (@lokka30)
        • Runs another rule, then continues on with the rest of the calling rule's actions.
        • Exactly like calling a function within another function when programming.
      • set-buffs (@lokka30)
      • set-level (@lokka30)
      • deny-level (@lokka30)
        • Makes it so a mob cannot be levelled (unless explicitly overridden).
    • Basic
    • Have it all tested by volunteers
  • Implement more conditions
  • Implement more triggers using additional listeners
  • Implement presets (presets.yml) (@lokka30)
    • Have it tested by volunteers
  • Implement groups (groups.yml) (@lokka30)
    • Implement group related actions (@lokka30)
    • Have it tested by volunteers
  • Plan out and develop Simple Settings. (@lokka30, @UltimaOath, @stumper66)
    • Have testers check Simple Settings works especially when combined with rules.yml.
  • Brainstorm how nametags will work. (@lokka30, @UltimaOath, @stumper66)
  • Work on custom drops. (@lokka30)
    • Custom drops was done well in LM4a so check out that redesign and implementation.
    • Implement CDs (@lokka30)
    • Have testers check the initial CDs system.
    • Work on actions for custom drops. (@lokka30)
    • Implement chunk kill count cap (@stumper66, @lokka30)
    • Have testers check the whole CD system including chunk kill count and the CD actions.
  • Work on integrations. (@lokka30)
    • NBT API (@lokka30)
    • Other integrations to work on?.. (unassigned)
    • Have testers check integrations work.
  • Work on Javadocs, basically all comments saying //TODO doc. (@lokka30)
  • Work on documentation.
    • We can't write the whole thing, otherwise release will be delayed a lot, though we should get it to a level where we list all options and tell beginners how they can use LM4.
  • Prepare changelog.
  • Prepare update announcements.
  • Release!
@lokka30 lokka30 added type: improvement Add or adjust a feature priority: normal Normal priority status: confirmed Confirmed by a maintainer status: in progress Work in progress labels Jun 11, 2023
@lokka30 lokka30 added this to the v4.0 milestone Jun 13, 2023
@lokka30 lokka30 pinned this issue Jun 17, 2023
@lokka30
Copy link
Member Author

lokka30 commented Feb 24, 2024

@stumper66 Should this issue be closed or repurposed?

@stumper66
Copy link
Collaborator

Let's close it since most doesn't apply anymore.

@lokka30 lokka30 closed this as not planned Won't fix, can't repro, duplicate, stale Feb 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: normal Normal priority status: confirmed Confirmed by a maintainer status: in progress Work in progress type: improvement Add or adjust a feature
Projects
None yet
Development

When branches are created from issues, their pull requests are automatically linked.

3 participants