#Custom element
1 messages · Page 1 of 1 (latest)
Wont happen
txAdmin is framework agnostic
This whole suggestion is weird, what is the purpose of this? I don't get it
So make an addon for this? it might work and it will be optional then
^
txAdmin doesnt have "addons" or something
Reduce from 2 admin menu to one for example
I have an administration menu on a F5 menu to manage everything that is ESX for the player and the other one that is TxAdmin for all the sanctions, whitelist and other
The correct way to write is txAdmin instead of TxAdmin.
Won't happen
Like i said, txAdmin is framework agnostic
Should never depend on a framework in any way possible
Plus you can just do the command and it's just as easy
kek
2019
to be fair that one idea was squashed and even deleted from code by cfx when we merged
@quasi sky Contrary to what yorick said, i actually want to add something like that, but it's very low priority.
@modest kindle We can still add them and still be framework-agnostic, we just have to provide an interface that every framework can use
Hmm im curious on how something like that would work tho
ok ty
yeah would not be easy
but doable
An API
To allow resources to define options
SHOWING information would be pretty simple
basically an tx api they would "register" their endpoint (maybe an export?) which would provide a markdown of a certain player
so when you click to open a player modal, tx would query the endpoint or export to get the data
but, to register buttons n such would be waaaay harder
Yeah
Unless theirs functions provided
To add buttons
But that is still alot of work and weirdness
Like a kind of "soundboard" idea but for buttons with functions attached
Is that how i should imagine it
something like that 🙂
Oh that would be nice
each