Open TonybynMp4 opened 1 year ago
I strongly recommend leaving the admin menu in the framework. txadmin is limited to what it can do.
I strongly recommend leaving the admin menu in the framework. txadmin is limited to what it can do.
didn't say to yeet the admin menu, just use txadmin's commands instead of using our own thing, no need to duplicate the same functionnality, especially since txadmin's is always being maintained
I strongly recommend leaving the admin menu in the framework. txadmin is limited to what it can do.
didn't say to yeet the admin menu, just use txadmin's commands instead of using our own thing, no need to duplicate the same functionnality, especially since txadmin's is always being maintained
I personally find myself using the qb admin commands more than the txadmin commands, in fact i find myself hardly ever using txadmin. Anyways, thats just me
what im saying is: having our own stuff that's not getting maintained and kinda sucks < using txadmin's maintained & supposedly pretty good systems, that does not involve getting rid of the adminmenu, just changing what the buttons do to call txadmin functions/exports instead, but i guess commands would change too? i don't even know if there's commands for bans etc. one thing that txadmin does better for SURE is no clip tho, that qb no clip is awful compared to txadmin's
This is waiting on the txAdmin API. Once released we'll take a second look at duplicate functionality we want to merge.
The problem
qbcore has it's own ban, warns and stuff so there's a duplicate wich is kinda useless (+ we're not really maintaining that stuff but they do)
Ideal solution
use txadmin's commands (bans, warns, whatever we can really)
Alternative solutions
No response
Additional context
No response