Error in Displaying Arabic Text in Ban Message on Roblox

Bug Reports Studio Bugs
,
#1

https://devforum.roblox.com/t/introducing-the-ban-api-and-alt-account-detection/3039740?u=7yooso

Description:

When using the Players.BanAsync function to write a ban reason in Arabic, the text appears garbled and unreadable instead of displaying correctly. This issue occurs only with Arabic text, while it works fine with English text.

Location:

This issue occurs in all instances where the Players.BanAsync function is used within our Roblox experience.

Time:

This error started appearing on June 26, 2024, at 15:00 GMT.

Images:

image

Reproduction Steps:

  1. Open Roblox Studio.
  2. Create a new experience or open an existing one.
  3. Use the following script to call the Players.BanAsync function with the ban reason written in Arabic:
    local Players = game:GetService("Players")
local player = Players:GetPlayerByUserId(1)

local config = {
    UserIds = {player.UserId},
    Duration = 7 * 86400, 
    DisplayReason = "لقد انتهكت إرشادات المجتمع",
    PrivateReason = "ملاحظة داخلية للسجل",
    ExcludeAltAccounts = false,
    ApplyToUniverse = true
}

local success, err = pcall(function()
    return Players:BanAsync(config)
end)
  4. Publish the experience and run it through the client.
  5. Note the message that appears when the banned player tries to re-enter the experience.

Expected Description:

The Arabic text in the ban message should be displayed correctly and clearly as written in DisplayReason.

Current Description:

The Arabic text appears garbled and unreadable.

Reproduction Files:

rbxl (46.2 KB)

8 Likes
#2

Definently a bug, however Id like to add that its probably best practice to write out your reasons, both display and private, in something like standard latin characters as they have a lesser chance of failing to parse through various systems including apis and your own external databases,

In the real world however, Roblox should automatically translate the display reason for users, but I dont know if that happens.

3 Likes
#3

Thanks for reporting the bug. We are actively investigating.

2 Likes
#4

We are confident that the bug is fixed now. If you see any additional issues, please file another bug report. Thanks!

2 Likes