#ANTI HBE SCRIPT

142 messages · Page 1 of 1 (latest)

paper eagle
#

Can we hurry up and implement a ANTI HBE / HBE banning scirpt?
Shits literally dirt easy to code.

#

-- Hitbox detection script
local Players = game:GetService("Players")

-- Define acceptable hitbox size range for each body part
local HitboxSizeLimits = {
["Head"] = {min = Vector3.new(1, 1, 1), max = Vector3.new(2, 2, 2)},
["Torso"] = {min = Vector3.new(2, 2, 1), max = Vector3.new(3, 3, 2)},
["Left Arm"] = {min = Vector3.new(1, 2, 1), max = Vector3.new(2, 3, 2)},
["Right Arm"] = {min = Vector3.new(1, 2, 1), max = Vector3.new(2, 3, 2)},
["Left Leg"] = {min = Vector3.new(1, 3, 1), max = Vector3.new(2, 4, 2)},
["Right Leg"] = {min = Vector3.new(1, 3, 1), max = Vector3.new(2, 4, 2)},
}

-- Function to check hitbox size
local function checkHitboxSize(character)
for partName, sizeLimits in pairs(HitboxSizeLimits) do
local bodyPart = character:FindFirstChild(partName)

    if bodyPart then
        local partSize = bodyPart.Size
        
        if partSize < sizeLimits.min or partSize > sizeLimits.max then
            return true -- Hitbox size is out of acceptable range
        end
    end
end

return false

end

-- Function to handle player character appearance
local function onCharacterAdded(character)
local player = Players:GetPlayerFromCharacter(character)

if player then
    if checkHitboxSize(character) then
        -- Take action: You could kick or ban the player here
        player:Kick("Hitbox manipulation detected.")
    end
end

end

-- Connect character appearance to the function
Players.PlayerAdded:Connect(function(player)
player.CharacterAdded:Connect(onCharacterAdded)
end)

#

--

#

could always delete the "take action" part and revamp the script to log suspecious users to a database, for sc to investigate/manually ban in the connect character to the function part

glass sable
#

dang

heavy bronze
#

Yap?

paper eagle
heavy bronze
#

No

glass sable
#

not a foreign language

paper eagle
#

heard thats pretty good, all tho outdated ^

heavy bronze
#

Luau is so confusing

#

I dont get it

glass sable
#

its not that difficult to understand what it means. just its difficult to write it

#

nxi what do you use to learn code

#

anything specific?

heavy bronze
#

I know how to code just luau is stupid

paper eagle
#

this

#

Learn the basics of computer science from Harvard University. This is CS50, an introduction to the intellectual enterprises of computer science and the art of programming. The course is taught live every year and this is the 2023 version.

💻 Slides, source code, and more at https://cs50.harvard.edu/x.

⭐️ Course Contents ⭐️
⌨️ (00:00:00) Lectur...

▶ Play video
#

25 hours long

glass sable
#

dam

rocky glade
#

i agree

#

god if u dont know how to code

#

coding looks like a whole foreign language

#

make it simpler

glass sable
spark matrix
#

cs50 is pretty good, came in clutch first year

distant mango
#

yes

#

chairman needs to make one

distant mango
#

but good idea

#

if a script can detect HBE better than a person then leave it up to a script imo

#

obviously include a logging system so SC can investigate or whatever but yeah

paper eagle
distant mango
#

really depends how accurate it is

#

if you can 100% detect HBE then just do an auto ban, people are not that good at detecting HBE unfortunately so yeah

#

if not then manual review

paper eagle
#

its really somethjing this game should have tbh

limber estuary
paper eagle
#

roblox hitboxes eg "humanoidRootPart" is always at a default set value

#

and if it is changed client sided, the script detects it

limber estuary
paper eagle
limber estuary
#

well it isn't because its connected to player added, if it were client sided that wouldnt be there

paper eagle
#

runs on the client end

limber estuary
#

well

#

it does

paper eagle
#

not really

limber estuary
#

¯_(ツ)_/¯

paper eagle
#
  • thats a very basic script
#

there is so much more that would need to be added into script to actually make it function

paper eagle
#

it is server sided

limber estuary
#

mhm

paper eagle
#

still dont see how that could impact detection

#
  • instead of automaticlly banning players
#

i will revamp this 100%

limber estuary
#

hence leading to false positives

paper eagle
#

but u can code script to check player every 30 seconds, and then if player comes back true (player suscpious) it can get added into database and store with points

#

a more sus player would have higher detection points

#

and a laggy player would be on a lower end

#

.
-- Log system with DataStore
local function logDetection(player, partName, currentSize)
print("[DETECTION] Player: " .. player.Name .. ", Part: " .. partName .. ", Size: " .. tostring(currentSize))

-- Save the player's suspicious activity in DataStore
local success, err = pcall(function()
    local data = suspiciousPlayersStore:GetAsync(player.UserId) or {Warnings = 0, Detections = 0}
    data.Warnings = data.Warnings + 1
    data.Detections = data.Detections + 1
    data.LastDetection = os.time()
    suspiciousPlayersStore:SetAsync(player.UserId, data)
end)
if not success then
    warn("Failed to log detection for " .. player.Name .. ": " .. err)
end

end

#

i dont code

#

but this shit is dirt easy

#

so clearly someone that actually codes for job can do a much better job of this

#

isnt gonna be very hard

shell yacht
#

or calculate the appropriate hitbox size with lag

heavy skiff
#

the creation of a proper anti hbe is tricky

#

you'd need to account for the shooter's ping, the server ping and the discrepancy

paper eagle
#

this isnt based on hit detection

heavy skiff
#

and then have a proper verification that would always return true but false when something's wrong even with all variables considered

heavy skiff
paper eagle
#

false positives would be minimal for a non hbe, whereas a user would be pinging every 15-30 seconds

heavy skiff
#

again

#

you check on the server

#

not on the client

#

you never do checking on client

paper eagle
#

it would be serverly

#

server sided

#

this is what head hbe looks like

#

it will check if a player has ultered hitbox sizes based on the default values

#

nothing to do with lag

#

nothing to do with getting shot

#

it just checks the values in this

#

and if values are ulted, eg this

#

it will flag a player add a point to the database, sc ect could review

#

all flagged players can be added to the database, and each time a player gets flagged, lets say 30 seconds per check, if true = +1 point

#

1 hour of gameplay = 120 times getting flagged

#

which means its pretty obvious someone is using hbe

rigid storm
heavy bronze
#

No.

paper eagle
#

yeah so

#

some improvements have been made

glass sable
#

wish i knew code like you

sick perch
#

If a person was never in that area but a shit fires there and damaged them lag doesn’t have an affect

#

That’s most cases of hbe in aegis

lusty willow
#

@paper eagle can you elaborate on how this isnt a banned suggestion

#

Implementing anti-exploit. We already have one, and it's constantly being improved upon.

paper eagle
#

its not anti exploit

#

its anti hbe

#

and i think we all know the anti cheat is shit

lusty willow
#

hbe is exploiting

#

thus anti hbe is anti exploit, no?

paper eagle
#

no

#

but

#

atleast there is effort in this suggestion

#

unlike the others

thorn matrix
sick perch
#

This game doenst have that good of an anti cheat

#

And the admins don’t give it credit when they let exploiters play unnoticed

rocky glade
#

thats y ur not banned

#

the exploit logs didnt find u

lusty willow
rocky glade
#

y blud say "we"

#

hes been an officer for like a day

lusty willow
#

🤓

sick perch
lusty willow
#

plus while unmoderated servers around like 4am were more common last year its recently been really hard to find a server that doesnt already have someone with mod on who could ban the exploiter

thorn matrix
sick perch
#

Ray6 guy

#

Had like 20 clips on him

#

Roblox banned him before aegis did

#

And Roblox never and cheaters for a century