The Ultimate Basic Admin Essentials Guide

Resources Community Tutorials
#23

And i’ve also got a question about the copy and paste are people allowed to edit the message itself? Or just copy and paste?

#24

People aren’t allowed to edit the message, however, those on mobile may be able to edit the logs as its a current bug where the TextEditable property does not affect mobile users, I’m pretty sure this applies to iOS users. Read-only TextBox issue with mobile - #7 by Flameysrs

2 Likes
#25

Hey I’m trying to make it so lists aren’t one line lists and show the entire message/command/whatever string it was in the list with text wrapped. I’ve fixed up the textbox to work in this way but I cannot seem to get the script exact, either the list is too small and doesn’t scroll all the way or at all, or the list is too large and has empty scrollable space. Note: i deleted the frame in the textbox (template) to have a nicer look, can you possibly make a section/help with this

#26

Actually disregard this, I’ve figured it out for the most part. One big thing I want to do, however, is be able to add the player argument to certain commands, like ones that display lists. For example ‘chatlogs flame’ will run chatlogs pre-run with the search for the corrected argument. It will check if the argument matches any players’ name and then search for that for example ‘chatlogs flame’ will run a search with Flameysrs. If the argument is not found to be matching any players, it looks for it in another list (I’ve created a command called leavelogs embedded into the mainmodule which created a list with the username of those who leave). If it cannot find it there, it just runs the search with the argument itself, in this case, just flame. Are you able to help with something like this?

#27

I’ve asked a friend who is friends with the BAE creator and he said that this function was never broken, cause it was never a function but people just created it themselves!

#28

Pretty sure the command bar has always come with Basic Admin Essentials but recently the autocomplete on it has been bugged. It happens even for groups using a non-forked up-to-date version of the module.

2 Likes
#29

@LegendOJ1 Do you know if you’re able to do this or help with this

#30

lmk if u still need help on this

#31

yes help would be appreciated with this

#32

Extremely helpful, thank you so much! Cannot wait to see the sticky message and new ban API implemented!

2 Likes
#34

When is the Sticky Message command coming…?

1 Like
#35

Does anyone know how I would add the moderator to the kick message:
image

Itd probably go "evocor moderation \n 406 \n You have been permanently blacklisted from SSS, you may not join this experience \n Moderator: \n Moderator note:

How exactly would I make it automatically put in the moderators roblox username?

Thanks

#36

This is a bit poorly worded but long story short, how do I add the moderator to the kick messages?

#37

For the migration to the new ban api I’ve spent a while trying to do so and this is what I’ve come up with so far and it does kinda work, any suggested improvements are welcome.

function Funcs.Ban(Args)
	local Player = Args[1]
	local playerPermissions = returnPermission(Player)
	local Victims = returnPlayers(Player,Args[3],Args[2])

	local Command = Args[2]
	if Command == "unban" then
		local UnbanConfig: UnbanConfigType = {
			UserIds = { playerService:GetUserIdFromNameAsync(Args[3]) },
			ApplyToUniverse = true
		}
		
		playerService:UnbanAsync(UnbanConfig)
	elseif Command == "ban" then
		if not Victims then
			remoteEvent:FireClient(Player,'Hint','Error',(Args[3] or 'nil')..' was not found.')
			return
		end
		for a,b in next,Victims do
			local victimPermissions = returnPermission(b)
			
			local banConfig: BanConfigType = {
				UserIds = {b.UserId},
				Duration = tonumber(Args[5]),
				DisplayReason = Args[4],
				PrivateReason = Args[4],
				ExcludeAltAccounts = false
			}
			
			if not sysTable.Permissions.Banned[tostring(b.UserId)] and victimPermissions < playerPermissions then
				sysTable.Permissions.Banned[tostring(b.UserId)] = b.Name
				pluginEvent:Fire("Ban Logs",{Player,"Banned "..b.Name})
				playerService:BanAsync(banConfig)			
			end
		end
	end
end
2 Likes
#38

Very helpful BAE Guide, thank you.

1 Like
#39

Hey owen! There is a way to bind the console bar into the top bar, needed the top bar module.

Just add into basic admin client

‘‘‘lua
local icon = (the code for the icon module)
icon.new()
:setLabel(“Silent command”)

:bindEvent(“deselected”, function()
:console()
end)
:oneClick()

‘‘‘

Wrote on my phone so might be wrong.
dm cuzangaming on discord if issues

1 Like
#40

If you’re binding the console button a topbar icon using TopbarPlus, you should keep in mind that you won’t be able to leverage the functionality that you can with the BindableEvent solution proposed in my original post, because you can’t open the console from outside of the module itself. With my solution, you can.

This is not a bad solution though - if you’re using TopbarPlus and don’t care about accessing the console outside the module, the following code will do it for you:

-- At the bottom of the Basic Admin Client LocalScript
local Icon = require(replicatedStorage.Packages.Icon)

local myIcon = Icon.new()
myIcon:setLabel("Command Bar")

myIcon:bindEvent("selected", function()
    myIcon:deselect()
    Console()
end)
1 Like
#41

Hello everybody. I am glad to find this active. Unfortunately, I was late in finding this guide and never knew what I could do with it. Furthermore, the module script has been locked and I did not have it saved in my inventory. This no longer works.

Does anyone have a copy of the module they could share? Does anybody know what happened?

Thank you.

#42

It’s in the toolbox if you click your inv, then click models then packages it should be there. I would show a video but roblox studio is down. Major Outage Affecting Several Components: Studio, Groups, Settings, etc

1 Like
#43

Thank you! Like I said, I did not have the module in my inventory. I was able to find a modified version on the forum though! Thanks.