refactor: unused varargs

[MoskalykA]

Hi, I suggest deleting this vararg which seems to be unused

[Gellipapa]

@MoskalykA Hi! What happens if somebody wants to pass some property of the item, or some extra variable that they want to get back in the callback?

function useHealthKit(source, item, healthRestoreAmount)
    print("Health kit used by player " .. source .. ". Restores " .. healthRestoreAmount .. " health.")
end

Core.UsableItemsCallbacks["healthkit"] = useHealthKit

ESX.UseItem(123, "healthkit", 50)

[Gellipapa]

So clearly we cannot accept it because we use it.

[MoskalykA]

I agree, although I haven't found any use for it (search), otherwise you'd have to use a table rather than a vargarg, and there should be a distinct difference in performance.

[Gellipapa]

I agree, although I haven't found any use for it (search), otherwise you'd have to use a table rather than a vargarg, and there should be a distinct difference in performance.

(SEARCH)
Just because you can't find it in public code doesn't mean that someone isn't using it, so you can't say that no one is.

Yes in the past a table might have been better but now you can still pass a table because of this operator, but if you don't add a table and overwrite or delete it you break the system.