To be honest, this is one of the best updates so far! Not only it fixes the line cutter glitch, but it also makes everything look so much cooler! I was thinking we could maybe get outlines to the bubbles… But anyway, this is a great feature!
On R6 rigs, the spacing for the text bubbles seems a bit too extreme.
On R15 rigs, with the same bubble chat setup, it looks like this.
Obviously, the bubble chat on the R15 rig is more identical to the classic bubble chat. I assume the bubble chat isn’t supposed to look the way it does right now on R6 rigs - it looks extremely out of place. Could you verify this behaviour between the 2 rigs @Chocopain ?
I verified that the size and shape of the HumanoidRootPart are identical on both rigs, as you mentioned that the bubbles are adornee’d to the HumanoidRootPart in one of your replies.
I made use of a LocalScript in the StarterPlayerScript container to enable the new bubble chat, in case you might wonder. I’m using default settings as well.
We never had to recreate any chat to customise the old version - we just had to playtest it in Studio and copy/paste the correct folder, which doesn’t seem that complicated IMHO.
This visual rework of BubbleChat is something we’ve needed for a long time. However I, like many other developers, will not be using it for the foreseeable future due to the fact that it’s now a CoreScript.
Chat forking is an extremely important feature to some games. While the customisation that we’ve been given is quite a nice feature, it still doesn’t come close to the freedom we had with forked chat. The simple ability to omit certain messages (/me, for example) from being displayed opened up a world of opportunities for custom commands and emotes. In fact, that’s a critical feature to many roleplay games. This update would be welcomed with open arms if it weren’t a CoreScript. This simple “Don’t like it? Change it.” philosophy should still be applicable to the new chat. Giving us the freedom to modify it to our liking would only boost developer engagement and would definitely aid the migration to the new system two-fold.
While it’s nice to have settings, a lot of us would prefer the total freedom to change whatever we want about the new system - whether it be adding custom commands and formatting or even just changing the tweening of the chat bubbles.
Will there be an optimization update for the Billboard GUIs?
One billboard will do a draw call which is extremely unoptimized for a game with hundreds of players and with UI corners that are also not efficient at all!
Decals got their textures batched and you can have a million of them without any performance cost.
My project mainly focuses on Billboards and it is already laggy with a small number of instances.
Question: Is there a way to make the chat bubble instantly pop up instead of sliding up? I prefer the old style of instantly appearing. Is there any way to make the new chat like this?
I like new style of bubble chats and I appreciate the efforts made by the staff who worked on this project but I think it would be extremely beneficial for all Roblox Developers if we had the ability to fork & customize it ourselves - rather than it being restricted within CoreScripts and limited config options.
While the visuals are nice and the config options provided seem okay for basic customization, how are we supposed to explore in-depth how this new product will work? Having thought Roblox were becoming more focused on user generated content, I would have thought full customizability would be provided for such widely used features.
Providing the new Bubble Chat as a fully editable product would seem like the best thing to do. Especially if you want developers to actually learn something - it could be used as a learning resource; helping people better understand how the chat system operates and even how Roact works.
I also think the player list and other on screen menus should have the ability to be forked & edited, but that isn’t really relevant here.
Will there be a native option supporting customization of chats for each player across all clients?
It’d be great to have a player with userId 000000 have a specific bubble chat color across all users.
I’m not sure of the implementation for Bubble Chat, but if we could do something like SetExtraData("ChatColor") like we can do for the existing chat, it’d be great.
ChatModule example of what I’m referencing:
SpecialChatColors = {
["879330134"] = Color3.fromRGB(0,109,176)
}
local Run = function(ChatService)
ChatService.SpeakerAdded:Connect(function(speakerName)
local speaker = ChatService:GetSpeaker(speakerName)
local player = speaker:GetPlayer()
local chatColor = SpecialChatColors[tostring(player.UserId)]
if (chatColor) then
speaker:SetExtraData("ChatColor", chatColor)
end
end)
end
I’ve been experimenting with this using custom models.
The VerticalStudsOffset property changes every time you change into a different character.
However, for VerticalStudsOffset to update, you HAVE to send another chat message.
My request is to make VerticalStudsOffset update when this setting is being changed, not when another chat message is sent. I don’t know if this counts for other settings aswell, but it does for this one.
Where I put this in?
local settings = {
– The amount of time, in seconds, to wait before a bubble fades out.
BubbleDuration = 15,
-- The amount of messages to be displayed, before old ones disappear
-- immediately when a new message comes in.
MaxBubbles = 3,
-- Styling for the bubbles. These settings will change various visual aspects.
BackgroundColor3 = Color3.fromRGB(0, 0, 0),
TextColor3 = Color3.fromRGB(255, 255, 255),
TextSize = 16,
Font = Enum.Font.Sarpanch,
Transparency = .1,
CornerRadius = UDim.new(0, 12),
TailVisible = false,
Padding = 8, -- in pixels
MaxWidth = 300, --in pixels
-- Extra space between the head and the billboard (useful if you want to
-- leave some space for other character billboard UIs)
VerticalStudsOffset = 0,
-- Space in pixels between two bubbles
BubblesSpacing = 6,
-- The distance (from the camera) that bubbles turn into a single bubble
-- with ellipses (...) to indicate chatter.
MinimizeDistance = 40,
-- The max distance (from the camera) that bubbles are shown at
MaxDistance = 100,
}
pcall(function()
game:GetService("Chat"):SetBubbleChatSettings(settings)
end)
This should not be built into the engine. This needs to be a standalone package that developers can easily drop into their game. This allows new developers to learn how modular code is written and it allows developers to have much greater control over the appearance and functionality of the chat. Building functionality like this into the engine is the wrong thing to do!
