Y.A.T.E.S - Admin Script / Framework
47 replies
Would you be more interested in using Y.A.T.E.S if there were videos about setting it up & coding for it?
Only registered users are allowed to vote
Yes | 70.37% (19) | |
No | 14.81% (4) | |
Maybe, I don't fully understand what it is yet | 14.81% (4) |
27 votes cast
20.10.15 05:18:20 pm





Please report any

This thread is meant for the discussion of Y.A.T.E.S, its features and suggestions. Please use the link above to create an issue report. Feel free to suggest current mods you would like to see as a plugin for Y.A.T.E.S. Note that this is not a scripting request thread.
List of known upcoming plugins:




edited 17×, last 13.06.18 03:32:29 pm
Definitely, worth it and a great work. This would beat any existent administration script out there on US.de File Archive.
@
Cure Pikachu: Right now it's already killed it, chopped it up and buried it six feet under


Too complicated for the layman
.
Maybe I will release Visual Admin that will have similar things + game settings.

Maybe I will release Visual Admin that will have similar things + game settings.
@
Yates: It might not be necessary here but I'm going to say it as a hint for when you make scripts in future.
The globals index stores values exactly like a Lua table does, and every time it has to lookup for values it does a operating which is similar to a pairs or ipairs loop, which means; if you add plain functions/values straight into _G like yates_say_prefix, that loop iteration will become slower. There are ways to trick that out by using tables, for example.
Is the best way to optimize the CPU performance because the code will need to look up for less values on _G, anything you add into a yates table will be iterated once and not every time you create a function/value unlike with the yates_ prefix.
@On-topic: I didn't read all of the documentation but from what I get you have to promote yourself to get the "admin rank", is there a console command to make that easier?

The globals index stores values exactly like a Lua table does, and every time it has to lookup for values it does a operating which is similar to a pairs or ipairs loop, which means; if you add plain functions/values straight into _G like yates_say_prefix, that loop iteration will become slower. There are ways to trick that out by using tables, for example.
Code:
1
yates.say.prefix = "!"
Is the best way to optimize the CPU performance because the code will need to look up for less values on _G, anything you add into a yates table will be iterated once and not every time you create a function/value unlike with the yates_ prefix.
@On-topic: I didn't read all of the documentation but from what I get you have to promote yourself to get the "admin rank", is there a console command to make that easier?
@
Gaios: You're turning out to be like Pygra.
@
Starkkz: I never thought of that, actually. Will be changed. Also yes there will be console commands as well as say functions which will do pretty much the same.
But when you initially start the script, it's not actually empty, it asks for the authentication token only the hoster can see which after authenticating gives you the permissions to use all of the commands. The basic group setup has already been done for you, so really if you want to quickly use it all you do is set yourself as the admin and you're done. Moderator, VIP and all those basic groups will already come packed with the script.
It's an "I'm lazy but can still do whatever I want when I want" setup.

@

But when you initially start the script, it's not actually empty, it asks for the authentication token only the hoster can see which after authenticating gives you the permissions to use all of the commands. The basic group setup has already been done for you, so really if you want to quickly use it all you do is set yourself as the admin and you're done. Moderator, VIP and all those basic groups will already come packed with the script.
It's an "I'm lazy but can still do whatever I want when I want" setup.

You're turning out to be like Pygra.
I meant CS2D's menu.

Maybe I will release Visual Admin that will have similar things + game settings.
>posting about own script in other threads
>pygra
Good luck bro!
keep it up!

CS2DArchive - Version Database www.CS2DArchive.com - WebHosting: www.BroHosting.eu
But that's a lot slower, more complicated, and unoriginal. Why click and browse a lot when you can just type?
And if you want to compete with this, why not make another thread about your own script?
The only reason to go "look at my work" on other people's thread is to help them or provide meaningful feedback.
And if you want to compete with this, why not make another thread about your own script?
The only reason to go "look at my work" on other people's thread is to help them or provide meaningful feedback.
good work, the replacing function takes all his sense with this oriented plugins script.
the dynamic group managment is a plugin right?, if I want to use an other group managment plugin it's still possible to replace the one you propose by mine?
the dynamic group managment is a plugin right?, if I want to use an other group managment plugin it's still possible to replace the one you propose by mine?
I hope that editing the actual script wont be too hard like HC Admin script which doesnt even look likes LUA.
It's hard being the best girl in the whole entire world
@
tontonEd: The code I am putting in now will mostly be core code, you can over-rule that code if you'd like. But I don't know why you would want to put in your own group management system seeing as the whole code of administration scripts is based on the group management system created initially.
But to answer your question, yes, it is possible. With a bit of hard work and wasted time sure.

But to answer your question, yes, it is possible. With a bit of hard work and wasted time sure.
The way it works is just genius, makes me want to delete most of the code of my script and copy your ideas. I would like to leave some suggestions and ask some questions though
About the say mode, why do you implement such thing ? I think you could just add a field to the players/group table like "canSeeDeadMessages" (or something like that) and make the rest automatic.
Also, you could add a description field for the commands.
And a group duplicate command or copy paste mechanics (lol, the level I'm taking it to).
@
Mami Tomoe: You probably don't know what Lua looks like.
About the say mode, why do you implement such thing ? I think you could just add a field to the players/group table like "canSeeDeadMessages" (or something like that) and make the rest automatic.
Also, you could add a description field for the commands.
And a group duplicate command or copy paste mechanics (lol, the level I'm taking it to).
@

edited 1×, last 21.10.15 05:36:27 pm
@
_Yank: I added the dynamic say settings to ensure no one has to code there. It's one of the most annoying things to have to redo for every type of server. Also this way people don't have to change group or player settings. Of course if force mode is not enabled there is a say command to force it upon only yourself or remove your prefix but keep your colour. This is for admins that may want to lay low and catch hackers.
I'll add command descriptions, nice idea. Also cloning will be possible. Both cloning into an existing group or in a new group. Thanks for the feedback!
@
Mami Tomoe: I believe it will be, of course no experience will not get you any far but this is with or without the script. But adding plugins to the script should not require a lot if not any knowledge at all of what it actually contains. You will work in your own files, not in the core. So it should be like creating any other script.
And for those who are wondering, because this script is going to be so big and unfamiliar, there will be a very detailed documentation and in-line comments. So don't worry!

I'll add command descriptions, nice idea. Also cloning will be possible. Both cloning into an existing group or in a new group. Thanks for the feedback!
@

And for those who are wondering, because this script is going to be so big and unfamiliar, there will be a very detailed documentation and in-line comments. So don't worry!