loops do not work

[Drago-Cuven]

any while loop or for loop seems to strangely enough completely stop JS and freeze the page until done. no errors are reported and i can't find a way around it.

for example:

local count = 1

while count <= 100 do
    print(count)
    count = count + 1
end

print("Loop finished.")

will technically work, but during the time its taking to print it all, it will completely freeze the page, any interactions with the page will go unnoticed, then when complete, everything previously done will just "catch up" all at once. i don't know how to fix this, or get around it.

here is the snippet of code that lua is run from:

async runLua({ CODE }, util) {
    if (!canRunLUA) return '';

    // Initialize Lua commands only once
    if (initWCSCMDS) {
        this.initLuaCommands(util);
        initWCSCMDS = false;
    }

    let result;
    try {

        result = await lua.doString(Cast.toString(CODE));
    } catch (err) {
        console.error(err);
        const msg   = err instanceof Error ? err.message : Cast.toString(err);
        const match = msg.match(/\[string.*?\]:(\d+)/);
        const line  = match ? parseInt(match[1], 10) : -1;
        let linemsg = '';

        if (line > 0) {
            const lines = CODE.split(/\r?\n/);
            linemsg = lines[line - 1] || '';
        }

        luaError.cur  = { msg, line, linemsg };
        luaError.last = { ...luaError.cur };

        // Clean the stack after error
        while (lua.global.getTop() > 0) lua.global.pop();

        util.startHats('DragoLua_onError');
        return '';
    }
    // Clean the stack after execution
    while (lua.global.getTop() > 0) lua.global.pop();

    // Check for invalid returns (functions instead of values)
    if (typeof result === 'function') {
        const msg = `Invalid return: received a function value instead of a result → ${Cast.toString(result)}`;
        luaError.cur  = { msg, line: -1, linemsg: '' };
        luaError.last = { ...luaError.cur };
        util.startHats('DragoLua_onError');
        return '';
    }

    // Reset current error state
    luaError.cur = { msg: '', line: 0, linemsg: '' };

    return result ?? '';

[RodrigoDornelles]

Are you sure about that?

[Drago-Cuven]

Idk whats going on. I'll send a video in a bit.

[Drago-Cuven]

Are you sure about that?

https://file.garden/ZM0obi0EPHK4dlF4/Screen%20Recording%202025-09-04%20144113.mp4

[Drago-Cuven]

you would "expect" the penguin to say the rest of the numbers while they show up in the console, but the page is frozen until finished, so the penguin only says the final result.

[Drago-Cuven]

although you can't see it in the video, if you try pulling a block, clicking the flag, or doing literally any interaction with the page, it just will not respond until the count is done.

[RodrigoDornelles]

@Drago-Cuven sure, so there's no problem with that, it's expected to be blocking, unless you fire an asynchronous js or something like that, you can give your software a breather by creating a loop block instead of using it internally.

[Drago-Cuven]

@Drago-Cuven sure, so there's no problem with that, it's expected to be blocking, unless you fire an asynchronous js or something like that, you can give your software a breather by creating a loop block instead of using it internally.

thats the thing, i AM running it asynchronously (or at least trying to.), sure loop blocks exist, but the point of this extension is letting you depend more on Lua than the blocks in general. this seems to be an ongoing problem since there even seems to be an ENTIRE FORK dedicated to fixing this, although i don't trust external content.

[ceifa]

It seems a problem on your implementation... the same would happen with plain JS if you are not using WebWorkers

[Drago-Cuven]

So web workers are required to make it work like that?

[RodrigoDornelles]

@Drago-Cuven Yes, this is a specificity of JavaScript itself, it has no parallelism.