Combat system

[kind bison]

I was wondering how to make a cambat system that requires a button to click for a simple m1 combo that also works for mobile

[wary meadow]

google how to m1

[signal cave]

this is a very complex thing

i think

never tried it myself

uh

you need to first detect when they m1

so

like

thats easy

events and stuff

then create a hitbox infront of them preferably from their HumanoidRootPart location

and play an animation

if another part in that hitbox's parent is a player then damage them

okay thats simpler than i thought actually

you gotta like, do slow and stagger and hitstun too, but thats not too much more

[kind bison]

Ok

This prob gonna take awhile to make

[viscid kraken]

Are you asking how to add mobile support specifically, or how to make an entire combat system?

[kind bison]

Entire combat system

[smoky marlin]

** You are now Level 3! **

[wary meadow]

yeah it is, until you actually finish it and realize there are input delays

and then suddenly learn that maybe cloning tsb isn't as easy as it looks

[signal cave]

oh right

[viscid kraken]

The amount of misery and suffering I experienced from this sentence is astounding

Fighting network latency and client to server to client replication times it pisses me off so bad

[signal cave]

making a gun script was so brutal when theres insane input delay

since i have to chose between the game being half unplayable or exploitable

[wary meadow]

we have server authority now so you don't have to make your own rollback netcode now

[viscid kraken]

True

I honestly don’t know how to feel about server authority

[kind bison]

I still don't know what I'm doing

[signal cave]

hang on

wait

so

uh

what is server authority?

because this gun script i wrote has brutal delays

[wary meadow]

google it

[signal cave]

what

please

i need to know🙏

this could be lifesaving

[kind bison]

I'm still confused how to make m1s

[viscid kraken]

google it

[viscid kraken]

remote events

@signal cave told u what to do soo

[signal cave]

google genuinley gave me absolutley nothing

[viscid kraken]

I guess you and I don’t use the same google? https://devforum.roblox.com/t/server-authority-how-to-begin/4139185

[wary meadow]

to be fair, google isn't very helpful if you're blind

[signal cave]

can you please like

recap it

wait

nvm

ill check out the link em sent

[viscid kraken]

I’ve known about server authority for a while but not how it reduces input lag, and still don’t see it

I figured it’s only an anti exploit measure

[signal cave]

soooo @wary meadow question

[smoky marlin]

** You are now Level 17! **

[signal cave]

can they still like

fire over false RemoteEvents

n stuff

[viscid kraken]

yes

[signal cave]

aw

[viscid kraken]

i mean i can’t tell you for sure but i highly highly doubt there’s any way to prevent that

[kind bison]

So what's a remote event

[wary meadow]

always assume exploiters have full control over the client

[signal cave]

gah

[viscid kraken]

roblox docs

[kind bison]

Okie

[viscid kraken]

🚪

[viscid kraken]

i used to exploit in like 2018 the amount of paranoia i have over client scripts lol

but back then filtering enabled didn’t exist either so

[wary meadow]

that's part of it, but imo that's not the primary benefit

[signal cave]

ok way

wait

so

if i calculated the ray for a gun fire on the client

then re-calculated it on the server

[wary meadow]

well see that's the thing. It doesn't reduce input lag. it's still there. you can't reduce it, or remove it. but what you can do is either move it somewhere else, or hide it. server authority, or more specifically rollback netcode in general, does a bit of both.

[signal cave]

would that work

[viscid kraken]

How come? The way I go about hiding lag in general is just being vigilant about hitbox calculation and prediction and having a lot of effects like visual effects animations etc masking the delay from your input to the server receiving it, I’m aware there are other ways but not on their details

[viscid kraken]

I mean yeah?

[signal cave]

ah

gotta do that later then

[viscid kraken]

A bit unnecessary if anything imo

[wary meadow]

ya that's how it's done but on a much bigger scale. like if you lock the player in place during m1 animation you can guarantee a reliable hitbox

[signal cave]

problem is with the shooter im making its a teleport-round-based rougelike instead of most normal shooters so i cant really moderate it

so it practically HAS to be unexploitable

[wary meadow]

but that's like saying you can get reliably raycast if you freeze the player for 0.2-ish seconds every time they shoot a gun, so obviously doesn't work everywhere

[viscid kraken]

not possible, if people wanna exploit they will. all you can do is make it costly to the point where it wouldn’t be worth for them to exploit

it’s the same story with obfuscation and encryption, if someone wants to crack something they will, you can only focus on strengthening encryption

[viscid kraken]

Yeah for sure but it’s not a sustainable way to just freeze players during attack in most cases

[wary meadow]

there is no security through obscurity 👍

[viscid kraken]

Wdym?

[wary meadow]

it's a saying, google it. rule of thumb when it comes to cybersecurity

[wary meadow]

ya so what rollback netcode does is gives you free reign to move where the lag happens

[viscid kraken]

In what way? Do you have any examples?

[wary meadow]

e.g in counterstrike you might find you'll sometimes get hit even when you're behind cover; only when you just moved there.

e.g say you have a shield that gives you invincibility when you click it; and another player shoots you. if you click your shield one frame after another player shoots you, your computer won't know that you got hit until [however long your ping is] later. your screen will show your shield activating, and then you randomly die.

this is PREFERABLE to clicking a gun and the shot happens latency later, or clicking your shield and it takes [latency] until it appears to activate on your screen

rollback netcode is what informs your client that you actually got hit

lag compensation is related but a bit different

lag compensation stops at the rollback stage, and basically decides if you hit the player where they were on the frame you actually shot, rather than where they actually are now, because the server doesn't know you fired a gun until [half latency] later

so there's this period of time where everything is in this awkward superposition state where all clients are guessing what happens on a particular frame until a few moments later when the details of what happened on that frame are received on the server and then propagated to your client.

[wary meadow]

*it's a big subject so you'll forgive me if i dont want to explain it every time some asks, it's not a beginner subject 😮‍💨 *

[viscid kraken]

I appreciate your explanation for sure, it makes a lot of sense! Do you have any links to where I can read more about examples and usages? I’m pretty knowledgeable about how the networking in games like csgo are, well before their subtick system anyway, so I did appreciate that example as well! Is there something you do in your code to purposefully redirect the latency or is it automatically done, and you build your systems around that?

[wary meadow]

google clientside prediction

[wary meadow]

also if you're "knowledgeable" about csgo's netcode you should already know about this... ;o

roblox's server authority is the same model

[viscid kraken]

I’m not super knowledgeable on the specifics but I know how things work in a nutshell, at a level where I myself know decently how things work, but not at a level good enough to explain it properly to others