Finding and reusing assets safely

How RoGenie looks for assets you already have before the Creator Store, scans store models' scripts in its insert tools, treats scripts in decorative and working models, and shows each creator.

On this page

Before RoGenie builds or inserts something new, it looks for an asset you can reuse: first your own, then free Creator Store assets. This page explains where it looks, how it checks Creator Store models, and what happens to their scripts. Everything here works on every plan, including Free.

Where RoGenie looks first

RoGenie's asset search looks in three places, in this order:

  1. This project. Assets RoGenie already put into this place.
  2. Your other projects. Assets RoGenie recorded for you in your other places, such as models from Roblox's mesh generator, models sent from Blender, images you uploaded and Creator Store models you inserted.
  3. The Creator Store. Free assets made by other creators.

One of your earlier assets counts as the thing you asked for only when every text it was saved with says exactly that: its name and the prompt it was made from, where it has them, must each give the same words in the same order as your search. Capitals do not matter, so "wooden crate" matches an asset named WoodenCrate. An "a", "an" or "the" before the first word does not matter either, so "the wooden crate" matches "wooden crate". Anywhere else, an article counts. Between two words, an article counts as a break, though which article it is does not matter: "lid for a pot" matches "lid for the pot", but not "lid for pot". Punctuation between two words counts as a break too: "car, door" is not "car door". An asset saved with neither a name nor a prompt, such as an image you uploaded, never counts as the thing you asked for. An asset that is only close, like "a weathered wooden crate with iron bands", is listed as a similar asset. A similar asset is never reused automatically: RoGenie checks it first, by its name or a picture.

When a candidate is turned down for a use ("not that crate, a smaller one"), RoGenie does not offer it again for that use in this project. It can still offer the same asset for something else.

The Creator Store

When RoGenie can use Roblox's official Creator Store API, through your linked Roblox account or RoGenie's own Creator Store key, it searches the Creator Store like this:

  • Free assets only. Never a paid item and never a plugin. RoGenie never spends Robux.
  • Verified creators first. Other creators are added only when there are few results.
  • More than models. It can also search meshes, decals (RoGenie then uses the decal's image), skyboxes and material packs.
  • A fit score from 0 to 100 for every candidate. The score weighs how well the candidate matches the search, the creator's verification and the votes, its triangle count for the job, how well its colours suit your art style, whether it has scripts, and how recently it was updated.
  • Triangle limits. Each mesh is judged on its own, because Roblox imports meshes of up to 20,000 triangles. A model with more than twice the triangles its job allows is dropped. A building may have more than a small prop.
  • One numbered picture. RoGenie looks at the top nine candidates side by side and picks one by its number. It makes that picture from Roblox's thumbnails of the candidates and keeps it in memory only. If the model you chose cannot see images, RoGenie uses stricter rules and says that the look was not checked.
  • Other people's words are marked. Each candidate's name, creator and description, and the numbered picture, reach the AI model marked as other people's data, never as instructions.

When RoGenie can use neither, or the Creator Store API is busy or fails, a model search uses the older Toolbox search instead. It finds models only, verified creators first, without triangle counts or fit scores. It does not mark the names, descriptions or thumbnails it finds as other people's text. A search for meshes, decals, skyboxes or material packs then looks only at your own assets. Your own assets are still searched first.

The script scan

Creator Store models can hold scripts, and some free models hide harmful ones. So when RoGenie's insert tools put a store model in with its scripts, RoGenie first scans every script of it:

  1. The RoGenie plugin loads the model into a holding area in Studio where no script can run.
  2. It reads every script (up to 200 KB each and 1 MB per check) and sends the text to RoGenie's server.
  3. The server checks the scripts against fixed rules and gives the model one verdict.
VerdictWhat it means
PassThe scan found nothing risky.
WarnSomething needs care, for example web requests, a check on a group rank, or code that players can reach through remotes or chat and that changes the game.
BlockA known danger, for example code that loads more code from outside (by asset id or as text), obfuscated code, a hidden admin backdoor, a remote that runs whatever a player sends, a purchase prompt, a teleport to a fixed place, data sent to a webhook, or code that acts differently in Studio.
UnscannableThe scan could not read the scripts fully, for example code that does not compile, is nested too deeply or takes too long to check. RoGenie treats it like Block.
  • RoGenie scans every time it checks or inserts a model. An earlier verdict never skips the scan.
  • The scan runs in RoGenie's own tools: Asset Probe and the insert tools. A model that RoGenie loads with its own Lua code is not scanned. RoGenie may load one that way, for example when Insert Asset by ID is off in Tool access.
  • When a search uses the Creator Store API, a model version that got Block in your own scan is hidden from your later searches for a functional asset. A search for a decorative asset still lists it, with its verdict, because a decorative insert deletes blocked scripts.
  • Plugins are never inserted.
  • The AI model sees the verdict, the rule ids and short, cleaned excerpts of the flagged lines. It does not see the whole scripts before the insert. After the insert, RoGenie still reads a kept store script as someone else's code, never as instructions.

The scan only finds what its rules look for. It lowers the risk but cannot remove the risk, so check what you insert before you publish your game.

Decorative and functional assets

What happens to the scripts depends on the job the asset does in your game. RoGenie picks the job when it inserts the asset:

  • Decorative (the default): a prop, scenery, a building or other structure, a showpiece, a character model for show, or many copies of one thing. These never keep live scripts.
  • Functional: a vehicle, a door, a tool, an NPC or a mechanism. These need their scripts to work.
VerdictDecorative assetFunctional asset
PassArrives without scripts; their text is kept as plain textArrives with its scripts working
WarnArrives without scripts; their text is kept as plain textArrives with its Scripts and LocalScripts disabled, and RoGenie asks you
Block or UnscannableArrives with its scripts deletedNot inserted
  • The plain text goes into StringValues under ServerStorage.RoGenie.Quarantine, one folder per asset. A StringValue cannot run.
  • In a flagged functional asset, ModuleScripts stay. They only run when a working script uses them.
  • When RoGenie inserts the top search result in one step (Insert Asset by Search), there is no scan first. A decorative asset then arrives with its scripts deleted, and a functional asset is not inserted.
  • One insert loads at most 10 different store assets. RoGenie names the ones it did not try.
  • Animations made by another creator do not play in your game. RoGenie tells you when a functional asset holds some.

So say what the asset should do: "insert a drivable jeep" gets a vehicle that keeps its working scripts when the scan allows it.

Turning flagged scripts on

When a functional asset arrives with its scripts disabled, RoGenie asks you a question like this one:

Creator Store asset 123456789 was inserted with its scripts disabled (scan flagged http_requests). Enable them?

  • Choose Enable the flagged scripts (the option ends with a short code, such as "(code K7QX2M)") and RoGenie switches them on.
  • Choose Keep them disabled and they stay off.

Only your own answer to that question can switch the scripts on:

  • Sub-agents and Discord runs cannot do it, and RoGenie cannot do it by itself.
  • With Ask the User off in Tool access, RoGenie cannot ask, so the scripts stay disabled.
  • The answer works once, within 24 hours. After RoGenie's server or your Studio restarts, RoGenie can no longer switch those scripts on, and it says so.
  • You can always switch a script on yourself in Studio: select it and tick its Enabled property.

Quarantined text is kept for reading only. To get working scripts from a decorative insert, ask RoGenie to insert the asset again as a functional one. It is scanned again, and you are asked again where the scan flags something.

How a model is placed

After the scripts, RoGenie sets the model up for its job:

  • Decorative models are anchored, their pivot moves to the bottom centre, and their collision is simplified: a box for props and scenery, a hull for showpieces and characters. Buildings, and meshes longer than 16 studs, keep their own collision so players can still walk in them. Props and scenery stop reacting to touch, but seats, team-change spawn points and parts that players click or drag keep what they need.
  • Functional models are left as they were built, so a car still drives.
  • If no job is named and the model holds working parts (seats, a Humanoid, constraints, prompts or moving joints), it is kept as built too.
  • A model is resized only when you ask for a size ("make it 12 studs long"). RoGenie never resizes it on its own.

RoGenie then checks the placement and gets a list of problems with the fix for each: a model floating above the ground or sunk into it, one blocking a spawn point, one covering another part's prompt, the wrong size for its job, or facing the wrong way. Models from Roblox's mesh generator and from Blender get the same checks.

Creators keep their rights

Creator Store assets belong to their creators. RoGenie inserts them under Roblox's terms, and creators keep their rights. RoGenie:

  • shows the creator of every candidate, and whether Roblox verified them,
  • keeps an inserted asset's own name, so you can see where it came from,
  • does not upload a store asset's files again and does not use them as references for new art.

The creator's name stays with each candidate in the results, so you can credit them in your game.

What RoGenie keeps

  • An asset record for each asset RoGenie puts into your places or uploads to Roblox for you, and for each Creator Store candidate you turned down. A record can hold the asset's Roblox ids, what it is and the job it does, where it came from (a store asset's creator, or the name and prompt of an asset you made), the Roblox account or group that owns it, the project and place, its path in Studio, whether it was kept or turned down and why, and its scan result. This is how RoGenie offers your own assets first and never offers a turned-down one again for the same use. A new chat about a place starts with a count of the assets recorded there.
  • The scan verdict and the ids of the rules that matched, for each version of a store asset. The script text is not stored.

Both belong to your account only: your verdicts never change another user's results. Deleting your account deletes them. See Privacy and data.

Tip

Do not want marketplace models at all? Say "no Toolbox models" in your wish or your standing instructions. Switching off the insert tools in Tool access is not the same: RoGenie may then load a model with its own Lua code, and the scan does not run on that path.

Back to top