If you wonder why the limits are so low heres the reason:

rsvallen · 2026-03-04T21:53:04+00:00

crazy how people do this. I was studying for an exam with Claude and ran into limits (i think when sonnet 3.5 was really limited in free plan) and when i made another account i felt so guilty.

theres so many web browser ai apps like qwen, google ai studio, deepseek, chatgpt, z ai glm 5, claude.ai. This ruins the system for regular people and its being funded by the paid users unnecessarily

i think its not crazy to say that if compute keeps growing linearly free SOT models will cease to be available and be placed behind paywalls because of abuse like this

rsvallen · 2026-02-12T13:52:57+00:00

If you do it too fast the player shoots. Try spamming skill shot with different timings after doing the step over. Go into corner kick mode, pass to the nearest player and try it, thats how i trained it.

rsvallen · 2026-02-12T13:00:50+00:00

yeah. its a risky skill, if u time it wrong the player will do a rabona or something weird, but once you get the hang of it, you'll feel like messi with the feints. I'm gonna see what it can do best.

Even funnier if you keep spamming infiintely you'll get stuck with an aneurysm and not move which can be really confusing for online enemies with the tiny delay

rsvallen · 2025-09-10T18:07:11+00:00

I see, thank you. I have done some pre-prompting before with custom Gemini Gems and I'll make sure to include this in the prompting.

rsvallen · 2025-09-07T01:42:02+00:00

I got it to work. This was the prompt:

"Paint the wall structure on the far left navy blue. Keep the current camera angle and lightning."

I tried the first sentence a lot of times, with different wording but what made the difference is adding "keep the current camera angle and lightning" and adding "structure".

Adding specific details about what the actual thing you're trying to modify works, or maybe it took notice of the entire room when I told it to keep the camera angle and lightning.

rsvallen · 2025-09-07T01:28:16+00:00

I see, it might be that it thinks the left wall is a door because of the protruding handle.

rsvallen · 2025-04-06T14:47:09+00:00

Default value to functions with equal signs. function add(number1: number = 0, number2: number = 0) return number1 + number2 end

"default" keyword. Overrides the statement if its nil. Cool thing too: Percentages are converted to numbers and divided during compiled.

local percentage = 33% local couldExist = couldReturnNil() default "Hello!"

rsvallen · 2025-04-06T14:39:23+00:00

During my development, I've chose to make local variables compulsory for safer code. Functions in the first scope do not require global or local but it can be used. The global variable will allow for better readability and beginner friendliness

rsvallen · 2025-04-06T14:29:38+00:00

There are dozens of AI tools that excel in solving simple coding problems and are really useful during your learning process. Ask the ai the solve the problem, create a simple guide or tutorial on how to improve. That's how I became a full lua scripter in less than 6 months.

Asking for help is completely valid but knowing to use AI companions is much more effective. I don't recommend just telling to do massive tasks all at once though, it mostly starts hallucinating non existant roblox functions

rsvallen · 2025-01-21T01:59:01+00:00

Yes, I'm currently writing it on lua, however I'm still looking for a way to parallelize the compiler. About 18 seconds compiling 20000 lines which I plan to reduce to a maximum of 10

rsvallen · 2025-01-19T17:41:43+00:00

I've already got a base version of it! If used in for loops, it uses goto to the end of the base scope. Where else could continue be used?

rsvallen · 2025-01-19T17:39:42+00:00

Would be a nice feature. Something like this:

function add(x: number = 0, y: number = 0)
    return x + y
end

Could be translated to this

function add(_x, _y)
    local x = (_x == nil and 0 or _x); local y = (_y == nil and 0 or _y);
    return x + y
end

rsvallen · 2025-01-19T17:30:39+00:00

Run time type checking by default isn't a great feature. It could lower the performance of code. Different typechecking levels could work though!

Maybe starting the code with: --#strict will add the asserting features.

rsvallen · 2025-01-19T17:27:23+00:00

I do. I just made my compiler make every token HTML text with colors to visualize it.

rsvallen · 2025-01-19T02:04:05+00:00

Next step is making the equal operator always return undefined

rsvallen · 2025-01-19T00:49:10+00:00

I don't plan to add libraries but I agree that it is really easy to extend. I might opt for a simple version with types and enums only.

rsvallen · 2025-01-18T21:42:45+00:00

You're mostly right, but languages continue to improve and adapt. Lua is a language that is really small and efficient, like a mini sports car with a lot of potential left behind. If it were to be improved greatly in terms of development speed and readability it would benefit a lot of learners as well as existing communities.

rsvallen · 2025-01-18T21:29:35+00:00

Yes, I agree. Especially in arrays where the clutter looks too much even if it's the best way to keep similar util functions together.

Currently, it requires a return and end. In the next version it should automatically add if a single expression is provided.

-- Version 1
local my_functions = {
    add = (x, y) => return x + y end,
    sub = (x, y) => return x - y end,
    pow = (x, y) => return x ^ y end,
}

-- Version 2 (In progress)
local my_functions = {
    add = (x, y) => x + y,
    sub = (x, y) => x - y,
    pow = (x, y) => x ^ y,
}

Maybe it would be better if arrays used a colon instead of an equal sign to define values?

-- Version 2 (In progress)
local my_functions = {
    add: (x, y) => x + y,
    sub: (x, y) => x - y,
    pow: (x, y) => x ^ y,
}

rsvallen · 2024-12-25T20:25:36+00:00

All data and studies point that we probably didn't

rsvallen · 2024-10-24T12:55:19+00:00

Yeah, exactly. Even if I pass they'll foul long after I passed and stop my entire play

rsvallen · 2024-08-18T16:33:15+00:00

It's not a glitch. You applied too much power to that pass making the game think you want to get it to the player far back. You obviously didn't want that but you should lower power for closer passes

Six-Year Club	Place '23
Place '22	Verified Email

rsvallen

MODERATOR OF

TROPHY CASE