Loot Table - Set Count Function doesn't return proper value

[PumpkinKnightStudio]

Expected behavior

With this following code used for randomizing value between 1-3

{ "type": "minecraft:empty", "pools": [ { "rolls": { "min": 1, "max": 3 }, "entries": [ { "type": "minecraft:item", "name": "stone", "functions": [ { **"function": "minecraft:set_count", "count": 0** } ] } ] } ] }

When using "function": "minecraft:set_count", and count to 0 in , it should return a value of dropped item even the there is no actual item drop. In this case the value should be between 1-3

For paper: The value always returned 0

Observed/Actual behavior

The value generated by ths command always returned 0 while using Paper Server, but doesn't happen in Vanilla

Steps/models to reproduce

Use the following code in Datapack Loot Table

{ "type": "minecraft:empty", "pools": [ { "rolls": { "min": 1, "max": 3 }, "entries": [ { "type": "minecraft:item", "name": "stone", "functions": [ { "function": "minecraft:set_count", "count": 1 } ] } ] } ] }

Plugin and Datapack List

This is part of the code in the datapack where
execute store result score @s run loot spawn x y z loot will set a value returned from the loot command

Paper version

This server is running Paper version git-Paper-496 (MC: 1.20.4) (Implementing API version 1.20.4-R0.1-SNAPSHOT) (Git: 7ac24a1 on ver/1.20.4)
You are running the latest version
Previous version: git-Purpur-2176 (MC: 1.20.4)

Other

No response

[electronicboy]

This is generally a spigot issue due to them removing empty stacks from LootCommand#dropInWorld due to their own mangling of ItemStacks, should be easy to patch, just needs a few minutes of testing than I can commit to right now

Well, actually, a trivial quick fix would probably be to just store the size of the list of stacks passed in