The current thread cannot use 'TS' (lacking capability Unassigned)

Help and Feedback Scripting Support
, ,
1

I’ve noticed that you now cant use anything in modulescripts, for example a module required by the client can’t even fire a remote event or a bindable, under the following error:

 The current thread cannot use 'TS' (lacking capability Unassigned)

I am not using sandboxed mode
image

A lot of other stuff fails like requiring another module, it used to work before, now it just doesn’t.

Does anyone know how to fix this? Any help is appreciated
I know I could probably fix it by messing with the sandboxed instance mode, but I’m not looking to use that

1 Like
2

figured it out, I had to set the sandboxed instance mode to experimental, then go to the module and check all capabilities and de-select sandboxed

1 Like
3

im glad you figured that out by yourself

while this is a security feature i agree that its very annoying because you don’t know its sandboxed until you change that workspace property

4

@EternalSerb Was this error from a Toolbox asset that you modified, an unmodified Toolbox asset, or other? If an unmodified Toolbox asset, can you provide the asset id? For sandboxing Toolbox assets we’re aiming to avoid errors from unmodified Toolbox assets that aren’t violating our policies.

5

Oh nah your script so done it has to pull out a ts

1 Like
6

Occured to me using Warp (networking module)