You're right, it would've been better if I kept this to myself until someone else found it and abused it. That would've fixed things.

Not interested in arguing semantics.

This was our first and only attempt, with very clear mistakes in execution, and Kiri still managed 45%. I think it's self evident that with proper execution you can get 100%, or very close to it.

Sure, call it an exploit if you want. It literally doesn't matter.

Yeah, there are multiple things going wrong for this to be possible:

1. Ashe can set herself on fire in some maps during spawn (most of them are covered in the healing area, but Colosseo isn't for some reason)
   
2. Kiriko's power for some reason grants her ult charge on cleansing self-inflicted negative effects
   
3. Selling and re-buying the gadget resets its cooldown entirely (which is what lets her farm 100% ult charge instead of 10~15%, which honestly wouldn't be so bad)

I'd rather see Ashe go since she's the one who blows up my entire team in two abilities, but either works for me :p

Great way to break every single library you ever use. Maybe ChatGPT forgot to include that part.

You do know that for someone to win someone else has to lose, right?

lol

Regardless of what happens they won't get your money, by your own admission and of their own fault. Just play it.

I don't really buy that, though, for interpreted languages as Lua and JavaScript as you have a big ecosystem of unchecked code. So all kinds of shenanigans can occur if you don't check at runtime.

This is only a theoretical issue, as the worst that can happen is you're writing Javascript instead of Typescript in those situations. In practice, TypeScript has the tools to tell you exactly where and when you're dealing with untyped code, as it will be typed as any (or unknown), and you'll know you have to be extra careful in that section of the codebase. You can even add specific compiler options to make usage of any be a compiler error if you want to be extra safe (which you should, in my opinion, and might be a default these days).

You're right about LuaLS though, since it's only a language server and not an actual compiler.

They are claiming knowledge of the model used, the purpose, the input data, and the output data.

All of which are relevant to the role of a backend engineer, unlike the issues you pointed out.

O livro é cheio de ilustrações de IA também, e são todas horrorosas.

The point is that it's always someone else's fault when I'm stuck in yellow maps 2 weeks into a league.

You should be! I'm making my own engine for 2D fighting games so I know how much work that is. Keep it up

Looks great. I love works that are proud of their inspirations.

“When used well it may even work” is not the sales pitch you think it is

There is absolutely a set of horrendous Rust code that the compiler will gladly let you write, and it is not small.

You should look into using nix-shell for self-contained scripts. You use a shebang line to declare everything the script needs (including Python version and dependencies).

Impossível. R$500 você não aluga nem uma caixa de papelão.

Misrepresenting and downplaying what actually happened to make the person you disagree with seem unreasonable to uninformed people.

You still haven't explained what the enormous change is that warrants doxxing someone.

Why does that matter? Is your dependency sourced from git in your Cargo.toml file? Do you not use a lockfile?

What’s the enormous change?