The kore's discuss from ayfri

Add donation/'support me' link

As a Kore enjoyer I'd like to send a cookie/pizza/coffee/diamond to our maintainers as a gesture of gratitude.

Could you add one of those to the project?

Add contribution guidelines.

You should create/write an contribution guideline.

Add Datapack to Kotlin converter.

This is a big feature that might be added one time, but not prioritized as very complex to create.

Add documentation to DSL module.

Simple documentation being added on all methods/classes/properties/typealiases.
Serializers might not be documented if only meant to be used once.

Update to 23w41a.

Add dust_plume particle type.
Change default datapack version to 20.
Reintroduce execute if function and return run commands.

Remove serialization from arguments as not needing anymore

As there is the asString() method, serialization is not really needed now.

Update to 23w40a.

Add Chat Components type optional enum property.
Change default datapack version to 19.
Make showEntity method of HoverEvent also accepts an array of Int as id parameter.

Update to 23w42a

Add source property to nbt chat component.
Add new jigsaw structure pool aliases feature.

Create `Gamerule` argument type.

Rebrand with a new, more complete identity

Find a new name, create an icon related to the name and rewrite the parts of the README where the name DatapackDSL is mentioned.

Generate the list of score criterion.

Add string manipulation datapack helpers functions.

Adding some functions that will be included in the generated datapack when used to manipulate strings (concatenation/splicing/looping etc).

Update to 23w46a

Add new scoreboard subcommands changes.
Update Scoreboard Displays to use the new subcommands.

Add exemples.

This will help a lot of people to understand the concepts of the library and how to use it.

Add scoreboard display manager.

Being able to define any content inside a specific line, only simple text components.

Add inventory manager.

Being able to define a list of item stacks inside any container at any slot.
Maybe also adding a way to define a behavior when clicking on the item.

Allow to use namespaces for each features.

For now, it is only available for tags.
This requires every generator to have a block parameter in the builder function.

Move recipes DSLs to their own files.

For example move fun Recipes.smoking to Smoking file containing the class with the same name.

Add special methods for `particle` command.

This is needed because the particle command arguments can have different usage depending on the particle type you put.
Certain types of particles can even have different states.
This is considered as high priority as it means that the current DSL methods are not totally valid

Source : Fandom

Reintroduce `generateZip()` method.

This function wasn't working because Minecraft didn't recognize the archive as a valid file.

Add unit tests.

Add unit tests for :

Update to 1.20.4

No changes are required.

Chore(issue): add issue template

I propose to add issue template to this project

We can have this template:

Bug report
Feature proposal
Question

Update to 1.20.4-rc1.

No changes are required.

Mistake in README.md

What happened?

In the exemple code in README.md, the pack block is outside the datapack. After trying it, I seen that it shouldn't be here.

What should have happened?

The pack block should be in the datapck

How can we reproduce this issue?

Try the code in the exemple and see IDE errors

extra-info

No response

Add DSL builders for common data types.

For example : ItemStack, BlockState, Entity etc.

Add builders for display entities.

Using JOML for matrix/quaternions/angles manipulation.

Refactor all DSL methods to be inlined when possible.

I'm not currently using a coding style where this is an issue, I'll change everything to improve code standards and optimize a bit.

Separate Argument interface into multiple files, investigate how that would be used.

I'm not a fan of having un-prefixed types like just Block, BlockOrTag etc, it could lead to bad imports or misunderstanding of the library, maybe just adding the word Argument is a good idea.
I will work on this when I'm decided.

Update to 1.20.3

No changes are required.

Add code KDoc.

Tasklist :

#22

Update to 1.20.2-pre1

Deprecate to ERROR level execute if function and return run functions until they return.
Add new map decorations.
Update default datapack version to 18.

Update to 1.20.3-pre1

No changes are required.

Update to 1.20.3-pre4

No changes are required.

Use block parameter syntax for all generators requiring one element from a list.

For example, DensityFunctions are currently created with the following code:

densityFunction("my_density_function", abs(2.0))

It will be refactored as this:

densityFunction("my_density_function") {
    abs(2.0)
}

Maybe investigate if it should throw an error if multiple functions for setting the type are used.

This will allow namespaces to be use simpler as every parameter of the Generator are usable from the lambda.

[BUG] Inappropriate argument in setEnchantments item modifier builder

Library version

1.0.0

What module does this bug apply to?

DSL

What happened?

I tried to use setEnchantments item modifier with its builder, but when i tried to add an enchantment to it I noticed that I cant do it. I looked at the source code and seen that in second parameter of function there is a Map instead of MutableMap and because of that it's impossible to add any enchantments.