LocalizationTools is not a valid member of CorePackages

my roblox studio auto updated at 1:03pm for me today while i was working on a project. ever since then I receive this error when opening a new window in studio:

image

i have not tried restarting my pc since the update.

repro steps: open a place in roblox studio

can post log files and/or specs if needed

34 Likes

Happening to me aswell, exact same error:
image

1 Like

Yup, I just got the reset 2 minutes ago. Even opening up a new Baseplate gives the same LocalizationTools error.

1 Like

Hey thank you for for the post. We are aware of this error. It is benign and a fix is on the way. Localization tools should still work.

17 Likes

Same error, looked it up to see if anyone else had it. Do you use the beta version? Just got member, this is my first reply! :smiley:

3 Likes

i do not use the beta version & i have not tried to repro this on beta. are you experiencing this on beta?

Never mind, I used to be part of beta but today I looked it up and found out that nowadays if you want beta it’s a different setting in the regular studio. I think I’m using the normal version.

Yep. I get this error every time I start and stop a game.
image

@rogeriodec_games it says “That page doesn’t exist or is private” when I click on your link.

@rogeriodec_games it says “That page doesn’t exist or is private” when I click on your link.
Because this topic is still waiting for approval by the staff…

Can we get an update on this please? I think this localization tools thing is causing my Roblox Studios Testing to malfunction. I been somehow flagging my player:Kick(). Where can I find the page that lets me know when Roblox updated Roblox Studios?

After this incident, an update was released in The roblox Studio, but the error still remains.

Is there a ETA on the fix for this or even a workaround?

This error is causing severe freezing for my game while using Team Create, and I am honestly not enjoying this one bit. As a work around, I created a folder in the BuiltInPlugins folder and dropped this plugin in there. The freezing has stopped (seemingly to do with trying to reload the entire plugin?) when I go to Play Test. I spent an aggravating hour today trying to figure out what was causing my issues and it primarily came down to either Team Create or this Plugin. After disabling Team Create, the lag persisted. I then removed the plugin and my development workflow has been back to normal.

This needs to be fixed now.

1 Like

I’ve been getting the same error too, and I think it’s causing some lag spikes.

This is now fixed. Thank you everyone.

4 Likes

Any Update on this? Because I cant do any mass testing with people./ The timing

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.