[Function Suggestion]: setstackhidden

[sixsevenblud]

Existing Functionality Check

• I have checked existing Luau and sUNC functions.

Existing Function Explanation

Env spoofing & manually hiding hiding stack levels is outdated.

Rationale

Setstackhidden solves this by being a builtin function that handles stack trace detections without luau implementations

Proposed Function Name

setstackhidden

Summary

https://docs.potassium.pro/api-reference/Closure%20Library/setstackhidden#setstackhidden
Hide a function from call-stack based detections.

Detailed Description

Not sure about any of the details of the function tbh, I just know that its extremely useful and already being implemented in plenty of executors

Example Use Cases

Prevent functions from detecting exploit caller
i.e (game function):
local Caller = debug.info(2, "f")
local Env = getfenv(Caller)

if Env then ... end

setstackhidden(1, true) -- prevents the function from seeing us as the caller
Also im gay

[altoidlol]

Also im gay

yeah no need to point it out folk

[sixsevenblud]

yea im also gay

[tiipolp]

Also im gay

yeah no need to point it out folk

[TypicaIity]

I'm gay and tight btw

[Richy-Z]

I mean, it doesn't necessarily make you undetected just by using setstackhidden

[altoidlol]

im gay and tight and oily and in need of assistance from a big buff oily man btw

[sixsevenblud]

I mean, it doesn't necessarily make you undetected just by using setstackhidden

Nobody said that brainiac

[avery-core]

#178

[TypicaIity]

I mean, it doesn't necessarily make you undetected just by using setstackhidden

Nobody said that brainiac

[sixsevenblud]

yeah mate read the post i hope you know i didnt say it makes you undetected lmao

[senS24th]

setstackhidden is currently not planned. Will maybe get added with time, depending on how much info we can get on it such as ways to detect it even if it's used, because afaik it's possible through some ways.

I'm personally not really that much into detections, so I didn't really try and go out of my way to look for these things. If people want to come and provide more ideas on how to test it, I don't see why not add it.

I just don't want to add functions which I know don't have a good base test. That's why there are barely any new functions being added. When deciding to add new functions, and if the function in question is something related to covering up detections, or functions which have a much higher testing potential, we tend to wait more to add them.

That's why, for example, getscriptfromthread was added, but actors not.

(Also, the actors API is outdated, and has other issues, such as being restricted to only working on actor objects. And if the objects are destroyed, you won't be able to run on the actor, even though you still can, if you get search and find its state)