From 479476561e5c9dbc0c0c4b7e4e0147683b26f7e1 Mon Sep 17 00:00:00 2001 From: Lucien Greathouse Date: Tue, 8 Oct 2019 16:16:06 -0700 Subject: [PATCH] Fix errors in 'Sync Details' page --- docs/reference/sync-details.md | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/docs/reference/sync-details.md b/docs/reference/sync-details.md index 3caa3da0..eeb88853 100644 --- a/docs/reference/sync-details.md +++ b/docs/reference/sync-details.md @@ -116,10 +116,18 @@ Meta files can contain: ### Meta Files to set Rojo metadata Sometimes it's useful to apply properties like `ignoreUnknownInstances` on instances that are defined on the filesystem instead of within the project itself. +If your project has `hello.txt` and there are instances underneath it that you want Rojo to ignore when live-syncing, you could create `hello.meta.json` with: + +```json +{ + "ignoreUnknownInstances": true +} +``` + ### Meta Files for Disabled Scripts Meta files can be used to set properties on `Script` instances, like `Disabled`. -If your project had `foo.server.lua` and you wanted to make sure it would be disabled, you could create a `foo.meta.json` next to it with: +If your project has `foo.server.lua` and you want to make sure it would be disabled, you could create a `foo.meta.json` next to it with: ```json { @@ -140,7 +148,7 @@ If you wanted to represent a tool containing a script and a model for its handle 0, 0, 0, 1, 0, 0, 0, 1, 0, - 0, 0, 1, + 0, 0, 1 ] } }