the "kb" is the knockback, it wont be destroyed for some reason.
#unable to destroy linearvelocity after creation
glossy sand
eager locust
dont use "wait()" its better to use task.wait()
"wait() is an older function that can be throttled by the engine, which means that the script might not run as expected. task.wait(), on the other hand, is a more modern function that guarantees the resumption of the thread on the next heartbeat step, without throttling."
that may not be the issue, but its worth a try
sly rose
the "kb" is the knockback, it wont be destroyed for some reason.
show more of the script
it seems like the kb.Active part is whats stopping the script
Active is a trait of LinearVelocities that basically just shows that it is on and actively being used in the Workspace
I believe if it has no parent it can move or is enabled under a part but in a non-workspace folder, Active will yield false and its only used as a status check to see if the velocity is affecting an object