Free model | Testing place | GitHub
THIS PAGE IS LIKELY OUTDATED
Due to Roblox’s plan to age gate the DevForum as of March 18th, this post is no longer maintained as I do not tolerate age gating to share open-source material. Open-source is open, and doesn’t deserve to be age gated to be shared.
If you want to ask a question, you’re invited to consult my GitHub’s discussions category. With a GitHub account, you’ll be able to suggest things, ask for support, and etc…
I am not abandoning Fork3X as a whole because it’s a project for which I still have fun and motivation to work on. Because it’s free, stopping it will have no influence on Roblox’s future, and is just a way to stop me from having fun developing.
Thanks for understanding my choice, and feel free to ask anything in the GitHub!
Current version: v3.2.0 [LIKELY OUTDATED INFORMATION; CHECK THE GITHUB]
Check the latest announcement here
Introduction:
Fork3X is a mod of F3X’s building tools that aims to offer a wonderfully simple set of tools, alongside better customisability and control.
This fork’s main goal is to allow developers to choose how they want their building tools to work, look like, and also to manage their game in a better way (if used in-game).
Note Fork3X doesn’t aim to surpass built-in tools, and should be used in studio only to simplify.
Some features inside Fork3X
- Marketplace Tool: mostly for in-game use, allows players to search images and meshes without opening the creator store.
- Text Tool: write text on parts, without headache.
- Transformation Tool: an unique union system that allows separation and saving without built-in tools.
- Many security features to prevent various issues (griefing, lag bombing)
- New UI system that allows optimal customisability.
- A bunch of settings that allows you to apply lots of tweaks in a single place.
- New features in tools here and there.
- Saving and loading: as of v3.2.0, reduces greatly the size of builds without missing parts (or, you know, of what I hope).
- Better mobile support: rectangle and soft selecting support out of the box.
- With APIs set up, no more F3X servers issues
- A few yet considerable optimisations, mostly regarding the explorer.
- A wiki: okay, at the time writing, there’s just a nothingburger, but I’m working on expanding it.
Is Fork3X BETTER than F3X?
It’s all about expectations.
Fork3X might be a more interesting option if you want a simple way to modify F3X (aka letting me suffer in my side), new features, fixes, and a wiki that’s still being worked on.
Use F3X if you don’t want a potential bug terrarium, but rather a rock-solid tool that’s promised to always work.
The best is to try both and see which one fits you.
I have raidRoleplay in my game, is Fork3X a good idea?
Although raidRoleplay is old, it seems to work very well when used with Fork3X. Just expect the log to not print actions done with the new tools.
How do I get Fork3X?
As you may know, Roblox’s moderation does an EXCELLENT job, and forbids Fork3X from being uploaded on the creator store.
Instead, I prefer sharing Fork3X in the following ways:
On GitHub (plugin and in-game):
Click on the latest version in the right tab, and install the file according to your needs.
For in-game use, insert the downloaded file by right clicking on the desired location in your game and selecting the file in Insert → Import Roblox Model (in the new UI, this might be different in the old one).
On Roblox (in-game):
Open the test place in studio, and find your desired version in ServerStorage → Version.
In order to mount the plugin, head to %localappdata%/Roblox/Plugins, and drop the file you installed.
Remember to check the Options module when used in-game! There’s a lot of stuff you can tweak, mostly the old UI (you can find out how in the Q&A).
Can I make my own fork of Fork3X?
Of course! Fork3X is under a public license (unlicense), which basically means “Here’s what I made, do whatever you want with.”
So, yes, you can make your fork, use it in your admin system, or even sell it (wait, no, don’t do it, bad idea).
Q&A:
Click the arrow to open the Q&A
Q: What are every new features in Fork3X?
Tools
Resize Tool:
• Scaling with the resize tool: keep proportions while resizing
• Mesh resizing
• Increments limitations will remain up-to-date with Roblox’s
Material Tool:
• Shadow and massless settings wit the material tool
• Every single new materials are added and will be added if Roblox adds any automatically
• MaterialVariants support (can be blacklisted)
• Previews (NOTE: If Roblox adds any material or if you want to add material variants, please check the wiki to add their resepective previews)
New Part Tool:
• Specific instances can be blacklisted in the Options module
• New creatable instances can also be added via the Options module
Mesh Tool:
• Without an API key nor HTTP requests enabled, you can convert any accessorie, gear, or mesh the creator owns to a mesh ID, a texture ID, and VertexColor in rare cases (the Firebrand e. g.)
• After setting up an API key, you can convert any meshpart or mesh to their respective mesh ID and texture ID
• If enabled in the settings, players can choose how they want a mesh to fit their part (if the mesh isn’t returned by the F3X servers)
Texture Tool:
• Textures and decals can now have their tint changed
• A new thumbnail mode setting (formerly fast mode) to display images of other kinds of assets (or even players)
• Decal IDs will be converted into image IDs in any situation
Constraint Tool (formerly Weld Tool):
• 3 new constraints: ropes, rods and motors (I advise you to be careful with ropes and rods in public servers as people tend to use them for bad purposes)
Decorate Tool:
• 3 new effects: highlights, selection boxes and particle emitters
Marketplace Tool:
→ This tool allows people to search decals (with the very bad InsertService:GetFreeDecalsAsync() function) without an API key, and meshes (and also a better search system) with one
Text Tool:
→ This tool allows people to put filtered text on their parts, along with various settings and rich text support
Transformation Tool:
→ This tool can create unions and intersections that can be saved afterwards (as long as it isn’t split)
Attachment Tool:
→ This (seemingly simple and useless) tool allows you to add and access a part’s attachments without the explorer, and so offer more possibilities with certain tools
Security
• Permissions (with CheckPermission and SetPermission functions)
• Anti-unanchor bombing
• Anti-effects bombing
• Anti-player deleting (yes, you can kick people that way + it might bug so be careful)
• Anti-player characters selecting (with PlayerTolerance)
• Anti-player ungrouping (protects from death loops caused by humanoids parented in workspace)
• Anti-mesh absurd sizing (creates Z-Fighting + regularly used by hackers)
• Image blacklisting
• Anti-events overflowing (so spamming events to crash a server)
• Doom-meshes protection (spamming meshes with high triangle counts will be blocked)
• A ConsiderPart function to not allow people to select specific parts and not consider them when pointing at them
• Prism selections (aka select parts in a part) won’t select forbidden objects anymore (mostly objects in terrain)
• Names given to parts in-game will be filtered
Optimisations
• Removal of getfenv() from the code
• Most deprecated functions are gone
• Replaced most functions from SupportLibrary with their Roblox counterpart (QueryInstance is included by the way)
• Major explorer optimisations
• A few optimisations in the selection rectangle algorithm
• Various changes in the tools’ code: use of BulkMoveTo, transition from Vector3 to vector, etc…
Miscellaneous
• Saving/Loading utility that can be managed from the Options module
• A grouping utility to make grouping and ungrouping more intuitive
• Better access to the built-in notifications system with V2 UI (just add any notification you want via CustomCoreConnections with the Core.Notifications table and Core.NewNotification event)
• A button for prism selection (aka select parts in a part)
• A rectangle selection toggle for mobile users (so their camera locks when rectangle selecting)
• Several improvements concerning the explorer’s children’s label
• Better documentation for multiple tools
• Themes and profiles to customise the UI
• Sounds (you can put their volume to 0 if it disturbs you)
• Attachments support
• Webhook support: send messages to a webhook through your own module or the built-in one (made by someone whose resource has been scrapped)
• Added an option to not cause handles to lock the camera
PS: this list needs to be update with v3.2.0. Sorry for the inconvenience!
Q: Your fork damaged my game!
Fork3X is under a public license, which means I take no responsibility on a misuse or aftereffects of Fork3X. You can get some tips for a good implementation below.
Q: How shall I implement Fork3X?
The UI is a major issue of a bad implementation of Fork3X. Use GigsDark (the old UI) first and make CementDark optional.
As a reminder, I’m a solo developer, and have very limited timetables. I cannot promise Fork3X to be 100% bug-free, so be careful to not implement it too quickly (keep F3X as an option).
Bug reports and questions concerning setting up certain things in Fork3X are always welcome here.
Remember to not make the security too harsh. Try to use a strike system instead, or just send messages via a webhook (yes, there’s built-in support!)
Q: How do I ... in Fork3X?
Note this is only a non-exhaustive list of “tutorials” that can be found in the wiki and in the replies here:
How to add previews for material variants
You have to add a “ColorMap” attribute to each MaterialVariant. You can simply set this up in a matter of seconds with this command:
for _, MaterialVariant in game:GetService("MaterialService"):GetDescendants() do
if MaterialVariant:IsA("MaterialVariant") then
MaterialVariant:SetAttribute("ColorMap",MaterialVariant.ColorMap)
end
end
This should be the result (this screenshot is pretty old):
How to modify a function in the core module
You will be able to find a list of each core module’s functions very soon. Stay tuned!
Once you found the name of the function you want to erase (Core.ExportSelection → ExportSelection), you can put its name inside the CustomCoreFunctions table, along with your new function.
If you just want to change the function, remember to add the keybind as a second argument in your table.
Here is an example where I changed exporting with a new function:
CustomCoreFunctions = {
ExportSelection = {function()
print("This shouldn't export if done correctly.") -- You can remove this tho.
end} -- OR end, "K"} if you want to keep/change the keybind (to K in this example).
};
Q: Difference between profiles and themes?
Profiles were the former nightmare fuel of customisability. It consists to:
- Drop two “Interfaces” and “UI” folders into another folder.
- Dive into 3 hours of mental struggle to add illogical attributes to make it work well.
- …look, it’s just bad, okay?
Themes are the new alternative that consists to modify the UI with components and a CSS (cascading style sheets) system. It’s just:
- Using a Roblox built-in tool to edit different types of UI item.
- Learn how to use selectors and be able to inject UI objects inside the UI.
You need little to no scripting knowledges to do so. You can even edit Roact (UI inside scripts very briefly) objects without Roact, which is really reassuring for most people (me included).
One of the first tutorials (after the API keys one) I’ll make will be centered on this. Stay tuned!
Q: What security features can be covered with Fork3X?
Taken from “Q: What are every new features in Fork3X?”:
• Permissions (with CheckPermission and SetPermission functions)
• Anti-unanchor bombing
• Anti-effects bombing
• Anti-player deleting (yes, you can kick people that way + it might bug so be careful)
• Anti-player characters selecting (with PlayerTolerance)
• Anti-player ungrouping (protects from death loops caused by humanoids parented in workspace)
• Anti-mesh absurd sizing (creates Z-Fighting + regularly used by hackers)
• Image blacklisting
• Anti-events overflowing (so spamming events to crash a server)
• Doom-meshes protection (spamming meshes with high triangle counts will be blocked)
• A ConsiderPart function to not allow people to select specific parts and not consider them when pointing at them
• Prism selections (aka select parts in a part) won't select forbidden objects anymore (mostly objects in terrain)
• Names given to parts in-game will be filtered
Q: I am using v3.1.1 or lower and experience build losses!
This is due to table encoding, modifying the way elements are saved when there are blanks. Everything should be fixed in v3.2.0 and above.
Q: Do I have to credit you in the description?
Doing so would be very nice, but it’s not necessary since credits are found in the building tools.
Q: I hate the new UI!
Even if v3.2.0 brings essential improvements to the UI, note that UI designing isn’t my thing and that it’s completely fine to not like it.
You can use back the old UI this way (from “Q: How do I … in Fork3X?”):
Q: Why do the yellow/blue/any color bubbles stay even after unselecting?
This is not normal. That’s a common tomfoolery of mine. Please report it here if it ever happens.
Q: How is Fork3X's code?
I’d consider it as average. Although there is no type checking, the code should be mostly clean.
Anyway, don’t tire yourself trying to find crap in the code. It’s just F3X.
Q: Can I use a module inside Fork3X for my own projects?
I will try by 2026 to extract a few parts of Fork3X and open-source them alone. This allows me to offer the cleanest samples for uses outside Fork3X.
Q: Can you help me for a project?
I know it’s an unserious way to say it, but I am not made for communities. At all. You’re better off checking tutorials here or ask how to do something.
Q: Can I change the number of save slots?
Yes! As of v3.2.0, this can be changed, along with size limits.
Note that Roblox has a built-in datastore size limit of 1 MB, so avoid going over this quota with all saves together, despite the server’s effort to encode and reduce the save’s size.
Q: Can I use my own serialization module?
This is a feature that will probably get added. In the meantime, this is very possible. Simply replace the latest serialization module with your module and everything should work as expected.
Q: Are there flaws hackers can use?
The only particularity a hacker has compared to players is firing high rates of functions, causing the server to lag.
If too many events are fired, throttling will occur, making spamming useless, in addition of general securities.
Q: I want to support Fork3X!
I don’t want to earn money from Fork3X. I totally develop it as a passion, so simply using it in your game is the best way to support Fork3X.
Q: Why is there no files in my Fork3X tools?
This is a problem in early v3.2.0 versions caused by the StoreFilesInPlayer setting.
I’ll quote the part of the announcement that addresses the forementioned issue:
Q: I want to contact you for something
I can be reached in the following ways depending on the scenario:
This thread (you need a DevForum account with a member trust level):
- Report bugs
- Give feedback
- Ask questions about Fork3X’s development and scripting
Private messages (you only need a DevForum account to do so):
- Small help requests (if you try to accomplish something with Fork3X)
→ I DON’T take commissions. I just don’t want to earn money off Fork3X, and if I have to work with people for free, everyone can hire me for free. This is something I want to avoid, hence why I will refuse any request.
GitHub:
- Bug reports
- Pull requests: if you know how to fix something, you can suggest your fix here
Q: If I update to the newest version, will my saves be erased?
No! Every saves will remain intact and loadable normally. Once you save again, anything that got added in v3.2.0 will be saved as well.
- They’re my daily building tools
- I use them eventually
- I know what it is, but I (almost) never use(d) it
- What’s F3X?
- I love the new UI
- The new tools are life changing
- Less lag
- More customisability
- The creator is helpful
- It makes things simpler
↓ (sorry for the typo)
- It’s buggy
- The updates aren’t frequent enough
- It’s less “optimised” than I expected
- The amount of settings disturbs me
- It has become viral now
- It’s more complicated than I thought
- I used the GitHub
- I used the testing place
- I’m experienced
- I’m a beginner
- I’m not a scripter
- Yes
- No
Thanks for reading. Feel free to write your feedback, doubts, and bug reports if you have any.
!
