dev

Oooh I can add them to the intellisense probably!

Add or sum 😉

Ah yeh

Was it mod or modulus? ceil or ceiling?

Yeah might be useful. not for the common ones but e.g. ceil

So no 'description' or exta info available :(

I can only access the name of them (and the raw code behind)

Do you think it'd be beneficial to show a list of all hlepers?

Great idea

Oh nice

and less prone to subtle changes that break commands :p

It'll be some more work to add examples but it'll make the system more robust

Then I can use that in the CSMM tests. If I make changes to the CSMM code, and the 'expected outcome' of one of the examples changes, I know I broke/changed some behavior

Which reminds me, I had this idea last night.

When I add the 'examples' functionality, I'd like to add the 'expected outcome' to those too

Though none of the tests broke, so I guess that was some indiciation that stuff remained largely the same

so possibility of some behavior changing is.. real

I took the existing system and broke it up into different pieces

Yeah I was worried for the same reason :p

I thought the difference was due to changes you'd made on staging and I was worried it was gonna break deadly air drops like, two weeks after I got them working again

But now I understand it at least I know what to expect

Yeah, would be good to be able to not have player data in

There should be different ones for cron, hook, commands, ...

As in, there's only one dataset

Yep, the data in playground is a bit 'dumb' right now

😂

I was just super confused as to why you said it couldn't be done and I was already doing it 😅

Yeah nice

Yeah because of the above

But you can make it work right now, right?

Cause those have been 'deprecated' for like 2 years now I think xD

The deadly air drops depends on it being able to make a command claim with a variable in the command

Perhaps in the future I can officially decomission the

${steamId}

${blabla}

variables

Yeh explains the difference between playground and actual use

Haha fair :p Kind of brittle I suppose

As long as the variable isn't populated it works

Got it

So again, doesn't see it's a player

Or a hook without a steamId indeed

Well as long as it's inside a cronjob, it wont fill in the data :p

But it's a hook that works on a logline which doesn't contain a steamId

I have it working currently

Ahhhh I see

Being "inside quotes" isnt gonna work, cause that would kill any usage like

say "hello ${steamId}"

One sec

Hmmmmm

I'm not sure how, syntactically

:p

😬

Can you fix it so it won't be filled?

If you would test the same code but inside a custom command, the steamId variable would get filled