Stop using load for a lookup table

[dmarcuse]

seriously who thought using load would be a good idea

[dmarcuse]

also it works for either numeric or string keys now

[dmarcuse]

why did you make a lookup table for this anyways why not just use string.char

[Luca0208]

The lookup table is so that you can just use lookup[stuff] with strings AND the number indexes.

[dmarcuse]

well i fixed it

[Luca0208]

I think what you have is a really good solution 👍

[dmarcuse]

just checked the git blame, I wouldn't expect anyone but @BTCTaras to use load instead of string.char and I guessed right

[BTCTaras]

haha ha

[BTCTaras]

uhh

[BTCTaras]

ha

[bauen1]

Hum what does the Revert button do ?

[dmarcuse]

dont even dare @bauen1 you're partially responsible for this mess too you know

[bauen1]

Uhm i left the load there because i though it had a reason to be there

[BTCTaras]

it was a temporary solution to a temporary problem and i accept full responsibility

[dmarcuse]

i'll fix the other lookup tables eventually too

[Luca0208]

Why can everyone press revert. I don't have write access why am I able to (in theory) revert it.

[BTCTaras]

that would create a fork where it is reverted iirc

[dmarcuse]

am i the only one that DOESNT have access to the revert button?

[bauen1]

XD

[BTCTaras]

yes because you own the pr

[Luca0208]

Probably because you already have a version

[dmarcuse]

later i'll make a proper metatable powered color lookup table

[Luca0208]

actually it's not because he owns the PR

[Luca0208]

That's the SCRIPT PR and I can revert