Yes spent thirty minutes changing the paths lol
No they recently removed that feature for the kick function
Roblox really needs to stop removing some of these essential features.
1 Like
I know right.
<30_Chara_Limit>
I think you can do something like
kick([[
title thing
you have been banned for (this) and (this) and stuff
]])
As I know, all new-line characters will be converted to spaces in kick messages. Also, kick messages will be limited to 300 characters. I can’t find the thread right now, but a staff member mentioned this. Not sure if it changed ever since.
Update; Newline Character doesn't work on kick messages - #12 by Tiffblocks
I’ll try this
<30_Chara_LIMIT>
I would advise against using this system, there are a number of substantial reasons for this, namely:
-
The Warning/Ban UI looks god awful (no offense) - orange text does not fit on a black backdrop, and is a total eyesore to any potential players.
-
There are a bunch of extremely basic grammar mistakes (e.g.
Our Moderation Team has determined that your behavior at Roblox Organization ... unproper);- Though, if you are not fluent in English, this is acceptable, but I would still advise you get a translator who can speak the language fluently to avoid making a fool of yourself on a public forum.
-
The actual panel looks horrible, a light-green background with white text is not complimentary and is a total eye-sore;
-
Any half-decent exploiter can just remove the LocalScript supposedly preventing you from “removing the ui” - to mitigate this, you should instead teleport them to a new place - bans are therefore meaningless;
-
There are a number of extremely basic errors, which shows the lack of your experience, such as
warning requested ...for a permanent ban button, which is visible in your ‘showcase’ - Showcases are supposed to be used for showing how well your product works, not showing off a poorly-tested panel that has conflicting text; -
Describing your product as the ‘new way to moderate’ is extremely over-ambitious, and is partially misleading; why do you have fifty UIs sitting in random scripts, this is horrible practice; and
-
Your scripting practices are god-awful, you check for three seperate types just when attempting to see if a UserID was entered, instead of just checking it against an ID for whatever reason? See Players:GetUserIdFromNameAsync
-
You also waste something around 1000 lines defining variables that you do not need to define and checking types multiple times instead of using Roblox’s native UI - I would understand doing this if it was a web application; it’s not.
-
You define variables such as the reason, the moderator and the userid when you could simply pass the data through to the server. See Remote Functions and Events
-
Also, having three datastores for warnings, temporary bans and permanent bans is an exceptionally bad practice, and should not be done - instead, pass an object through the table, defining
{warnings: {}, bans: {}}, etc, and add a duration field on temporary bans… -
You have six different scripts (besides the API), each taking up over 500 lines unnecessarily through poor practices, therefore, this module becomes an egregious memory hazard if the Developer continues to develop it like this
-
The handling is some of the worst I have ever seen, the Developer checks every five seconds whether a person has “removed” his UI, now, this is a server-script, so I don’t need to say why this is going to cause a spontaneous memory leak.
-
The Developer, and I am not joking, does this for every theme, so you have functions which do the same purpose being listened for twice, depending on the theme the user has chosen.
-
The Developer, and I am not joking when I say this, handles kicks in the aforesaid manner; having three functions for kicking players depending on the user-selected theme.
-
-
I digress, as aforesaid, don’t use this module until the Developer fixes the serious security issues with this module. Instead use suitable alternatives like SimpleAdmin or Adonis - In my opinion, @crywink’s SimpleAdmin is better.
5 Likes
For everyone here, I recommend to avoid using any products & services from Session 42 as after doing some digging, all of their projects end up having major security issues and bugs and not long after they release, they all get discontinued.
For more information of why this module is a wrong choice, check the reply by @AwesomePIays.
That’s a serious accusation. We had 3 products. One of them was discontinued. Claiming “all” products get discontinued is totally off. It’s clear that you didn’t do any “digging”, but just came up and posted your random opinion. Both Blueberry and Atherum are fully, and 100% operational. There were hours of work, so coming and telling “everyone” to avoid using our products is just disrespect. All of our products are free and we get or lose nothing if you like or dislike them.
You did the exact opposite by the way.
Anything that does not kick instantly is a flaw. There is no point to have a “better” GUI for the banning.
Your best bet to making a custom kick GUI is to completely blacklist the player from accessing your game’s remotes and block chat, etc. from serverside, and also kick after 60 seconds.
This is a decent project, but no point to use. Good job on it though.
1 Like
Well, what I meant by discontinued is that Ive seen most of them end up with final update replies saying stuff like “Due to a negative amount of feedback…” which means clearly that you are discontinuing the project.
Both Butterfly and that alt detector I forgot how is it called got discontinued at the end of the day. Now im waiting for this to get too since I know what is gonna happen.
Atherum (Alt-Detector) never got discontinued, Butterfly got discontinued due to some issues the Development Team couldn’t reproduce/fix.
1 Like
Blueberry will not be discontinued because it works as expected and people are okay with it. We give our best to keep it alive.
Atherum had indeed a negative response, but we still won’t discontinue it unless there is an unfixable bug that we can’t find a solution for. All we did was publish an article about what we had in mind when we started it.
Im gonna leave you guys alone since you clearly have a lack of proffesionalism when it comes to managing your projects.
If you aren’t good enough for the Community Resources category, just dont use it.
1 Like
Thanks for the detailed, yes disrespectful opinion. Let me explain.
Telling people not to use it is literally conflictual. Many developers use it and it works great for them.
First things first; Blueberry was my very first product. I published it because I found it nice and because I was proud of it.
I am not gonna lie, it works very well. Despites the bad and useless usage of scripts.
Sad. People can change it. That’s the point. In fact, the UI is only meant to be an example.
Blueberry is distributed for free. Meaning I won’t pay a translator for a few lines or text. Again, the UI is meant to be an example. As you might have or might have not notices, some people actually made their own UI. I’ll consider hiring a translator if I ever make profit.
It’s all about taste. Many people liked it. Additionally, the panel wasn’t even planed. Blueberry was meant to be API-based only.
I basically explained this 12 times now. The UI can be bypassed and there is no way to avoid it. However, the exploiter’s character will still be removed and their chat will be muted. You will probably say that this isn’t enough, but it is if your RemoteEvents are getting checked on the server.
That literally doesn’t matter. But okay, I’ll agree with you on this one.
It was a concept, an idea of a new way to display punishments. Again, I published this as my first model. Obviously the “scripting practice” wasn’t amazing.
At that time, it was the only way I personally could do it. Now, I could probably make everything inside 2 scripts. However, I don’t see a problem with that.
Claiming that memory usage is high is unfair. It isn’t high. You can check that.
I will not change a whole set of scripts just because you and a few other don’t like it. Blueberry works wonderful for so many users.
Thanks again.
I’m just shocked at the amount of hate you’re getting. Like wow.
1 Like
Getting a translator for a few lines when you don’t make profit is a horrible idea. Also, you aren’t a fool if you can’t speak English fluently when it isn’t obviously your native language. Don’t judge people on their ability to speak a foreign language, that’s ridiculous.
That’s where we agree. Although it seems like the developers like the theme for the UI, which is absolutely fine. You are free to love what you want.
This claim was so said many times that it feel useless. However, UIs are unsafe by nature, but blueberry seems to solve this by removing any interaction between the server and the suspect.
I agree with the points you brought about the scripting practices that were used in blueberry.
While I can understand the fact that awesome’s reply can be seen as disrespectful (in fact, I remember flagging his second reply because it was inappropriate), I still agree with the fact that blueberry is bloated with many scripts that shouldn’t exist. I suggest you to redo it while considering awesome’s scripting-practices-related points, it would be better for you and your studio’s reputation, not only the consumers.
1 Like
We have released a rewritten version of the system to end everyone’s concerns about optimization, style, and security;
1 Like