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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LM4 Testing Super-Issue #428

Open
lokka30 opened this issue Nov 6, 2022 · 0 comments
Open

LM4 Testing Super-Issue #428

lokka30 opened this issue Nov 6, 2022 · 0 comments
Assignees
Labels
good first issue Great choice for new contributors help needed Contributions appreciated priority: normal Normal priority status: confirmed Confirmed by a maintainer status: needs testing Testing must be done to close the issue type: improvement Add or adjust a feature
Milestone

Comments

@lokka30
Copy link
Member

lokka30 commented Nov 6, 2022

Notice: LM4 testing is currently suspended as we are rewriting the plugin in Kotlin.

Quick Links: LM4 Wiki; User Feedback Forum on Discord

LevelledMobs maintainers are seeking user testing to ensure that the release of LM4 will be suitable for production server use from stability.

This issue provides a list of things we'd like testing and feedback on.

Required Test Server Configuration

  • Client and server running MC 1.19.3.
  • PaperMC or PurpurMC server software.

LM4 currently lacks the required code to provide compatibility for the SpigotMC server software, and MC 1.18.2. It will be quite an effort to port the code base, so we are prioritising to make sure LM4 works correctly on the recommended server configuration before we begin compatibility work. Yes, LM4 will have this compatibility by the time it is released.

Please read this Q/A:

  • What needs testing?

    • This is outlined in the rest of this Issue page. Stay tuned!
  • Who and where do I send my results / feedback?

    • Where: The user-feedback forum channel on the ArcanePlugins Discord guild. Create a new post there to discuss. 😃
    • Who: Tell @lokka30 on the Discord guild the results of your testing. Include:
      1. What you've tested.
      2. What you've observed.
    • Even if everything seems to work as intended, we'd like to hear it!
  • How do I test LM4?

    • It's super simple: run it on your server, and check it out! Play with settings and if something breaks where it shouldn't have, let us know.
    • We'd also like to hear what you think of the plugin in general, so that we can make major breaking changes before we release LM4. So, keep your eyes peeled for anything you would like to have changed in LM4.
  • Why do we need to test LM4?

    • None of LM4's code has been battle-tested like LM3's code has. We want to make sure we iron out as many issues and address all of your feedback before we pull the magic lever to release LM4 for production server use.
    • The reason we want you to test LM4, is so that we can gather your feedback, and users manage to break things in interesting ways. ;)
  • Is there anything I can do in addition to my testing?

    1. Send us any feedback you have on the plugin's alpha stage, or just a thumbs up if you think it is brilliant.
    2. Send us what you'd like to see in the future from LM4. Even if it's already on the issue tracker: it would be nice to prioritise things which are more requested than others.
  • LM4 seems very bare-bones for how long it has been developed. Will the final product be like this?

    • No! This is an early look at the fundamentals of LM4, it's in alpha stage. You'll watch it grow, and we hope you'll be involved with that.
    • LM4 has had on-and-off development, with most work occurring in late 2022 onwards. It is a hobby project. "These things, they take time". LM4 has undergone a few re-writes in itself, it's just how things roll when perfectionists are in charge.
  • I'm confused how to use LM4, can you help me?

    • You might find your answer on the very early stage of the LM4 Wiki. :)
    • If not, @lokka30 on the Discord for help, just make a new thread in the same forum channel.
  • Where is the rules file? Where can I change how things work?

    • We've replaced the Rules System with something very similar, called the Functions System. It is in settings.yml now. It is slightly different to the Rules system you are used to.
  • What do I get out of this?

    • Unfortunately, we are not billionaires - so we can't pay you guys. But, we can offer you a special Testers role on our Discord guild, and your name written in the Credits page on our Wiki. You'll also take part in ensuring you get a better end-product when we release LM4. We hope those are sufficient for you. ;)

What needs testing?..

Everything!

  • You might first find it useful to check out the plugin and try configure things to see what happens before you begin testing it.
  • Play around with all of the configuration files, explore what you can do, and see if all of the features work as
  • If you don't have much time on your hands, we'd also like to hear that LevelledMobs 4 works out of the box as you expect it to.

Compatibility

SpigotMC (not PaperMC) Compatibility

LM4 is developed and tested using Paper, but we aim to also provide compatibility with Spigot servers.

We'd like to make sure that all features of LevelledMobs work on Spigot implementations, except where specified otherwise (such as with mob skulls in custom drops).

  • Chat messages sent by LevelledMobs

    • e.g., when running /lm about and other commands.
  • Labels

    • Packet labels (set-packet-label action)
      • When forcefully using the ProtocolLib label handler, is it working correctly?
    • Permanent labels (set-permanent-label action)

LM3 -> LM4 Conversions

  • For servers which used to run LM3, and switched to LM4, were there any issues?

    • We're especially interested with those who used things like usedroptable: XYZ and other entity-specific persistent data, since we want those to migrate properly when using LM4.

Features

Functions System Features

  • Spawn-Distance and Y-Axis Levelling and Basic Levelling Strategies. Do they work as expected?

  • Make sure ExitProcess, ExitFunction, and ExitAll actions are working.

    • Specifically, we need to make sure the exit status from the previous run of any function/process is not carried over.

Custom Drops System Features

  • Custom Model Data

    • If anyone has the capability to test the Custom Model Data feature in Custom Drops, please do so and let me know if it works properly. I don't have any resource packs or plugins which use custom model data.
  • add-drop-tables, set-drop-tables, and remove-drop-tables actions

    • Check that these actions set the correct drop tables to levelled mobs.
    • Check that these drop tables are being applied in custom drops to the levelled mobs.

Miscellaneous

  • Check if the on-entity-scan trigger is being fired when the scan task is enabled
    • Enable the scan task by adding this to settings.yml:
advanced:
    scan-task:
        enabled: true

This issue's conversation is locked as this issue's conversation section is not a suitable medium to discuss test results. Please use our Discord instead.

@lokka30 lokka30 added type: improvement Add or adjust a feature help needed Contributions appreciated status: needs testing Testing must be done to close the issue priority: normal Normal priority status: on hold Other things need to be resolved before progress can continue good first issue Great choice for new contributors status: confirmed Confirmed by a maintainer labels Nov 6, 2022
@lokka30 lokka30 added this to the v4.0 milestone Nov 6, 2022
@lokka30 lokka30 self-assigned this Nov 6, 2022
@lokka30 lokka30 pinned this issue Jan 14, 2023
@ArcanePlugins ArcanePlugins locked and limited conversation to collaborators Jan 15, 2023
@lokka30 lokka30 changed the title LM4 Testing LM4 Testing Super-Issue Jan 15, 2023
@lokka30 lokka30 removed the status: on hold Other things need to be resolved before progress can continue label Jan 15, 2023
@lokka30 lokka30 unpinned this issue Jun 17, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
good first issue Great choice for new contributors help needed Contributions appreciated priority: normal Normal priority status: confirmed Confirmed by a maintainer status: needs testing Testing must be done to close the issue type: improvement Add or adjust a feature
Projects
None yet
Development

No branches or pull requests

1 participant