Adding both .daytime and .dimension condition to a recipe doesn't work

[TomPlop]

Checked for existing issues

• I have checked for existing issues, and have found none.

Tested latest version

• I have checked that this occurs on the latest version.

GregTech CEu Version

1.6.4

Minecraft Version

1.20.1 Forge

Recipe Viewer Installed

EMI

Environment

Singleplayer

Cross-Mod Interaction

No

Other Installed Mods

Ad Astra, Architectury, Botarium, EMI, Gregtech, KubeJS, Resourceful Lib, Resourceful Config, Rhino

Expected Behavior

I'm making a recipe for solar panel that should only work in the moon dimension from Ad Astra and during day time. After having issues with the solar panel recipe I tried other recipes to test all of them have the same issue.

event.recipes.gtceu.assembler(id)
            .circuit(circuit)
            .notConsumable(InputItem.of(input))
            .duration(200)
            .daytime(false)
            .dimension('ad_astra:moon')
            .EUt(-128)

        event.recipes.gtceu.assembler('kubejs:test')
            .circuit(2)
            .notConsumable(InputItem.of('ad_astra:solar_panel'))
            .itemOutputs('minecraft:oak_planks')
            .duration(200)
            .daytime(false)
            .EUt(32)
            .dimension('minecraft:overworld')

Actual Behavior

I'm getting an error and kubejs stops to run anything in the file after .dimension . Wherever I put the .dimension it will stop generating after it. If I test by removing one of either .daytime or .dimension the recipe will work. But when together it won't.

server.log

Steps to Reproduce

Download a fresh instal with Gregtech, KubeJS and EMI.
Create a recipe that uses both .dimension and .daytime condition
Reload your server_scrit or relaunch the game

Additional Information

I tried every recipes even the most basic one, every time I have both .daytime and .dimension kubejs will stop generating recipes after .dimension (if I put it at the end the recipe generates without the .dimension condition)

[screret]

oh, known issue, already fixed too

[screret]

the fix is to use a dev release from github's "releases" page