+
+If the script is using `--!native` but a function doesn't show the `
+
+## Limits and Troubleshooting
+
+Compiling code into instructions for a particular CPU requires additional storage memory. Additionally, optimizations for complex functions may take too much time to perform. Hitting an internal limit will report an error in Studio's [Output](../studio/output.md) window, including:
+
++_Function 'f' at line 20 exceeded single code block instruction limit_ + +This error means that a single block of code inside a function used more than 64K instructions. This can be avoided by simplifying the function or by splitting it into individual smaller functions. ++ +
+_Function 'f' at line 20 exceeded function code block limit_ + +This error means that a single function contains more than 32K internal blocks of code. Internal blocks of code do not exactly map to the control‑flow blocks in your script, but this error can be avoided by simplifying the control‑flow in the function or by splitting it into individual smaller functions. ++ +
+_Function 'f' at line 200 exceeded total module instruction limit_ + +This error means that, in total, the function has reached a limit of 1 million instructions for the entire script. In some cases, the reported function itself may have a lot of instructions, or the limit may have been reached by functions earlier in the script. To avoid this issue, it's recommended to move particularly large functions into a separate non‑native script. You can also try marking that separate script with+ +`--!native` , but 1 million instructions takes up a lot of memory and you may exceed the memory limit. +
+_Function 'f' at line 20 encountered an internal lowering failure_ **(or)**+ +
+_Internal error: Native code generation failed (assembly lowering)_ + +Sometimes a function contains complex bits of code that the native code compiler cannot currently handle. To avoid this error, inspect complex expressions in the code and split them up or simplify them, but also consider opening a bug report with an example of the code that failed for this reason. +
+_Memory allocation limit reached for native code generation_ + +This error means that the overall memory limit for native code data has been reached. To avoid this, try removingdiff --git a/content/en-us/production/analytics/analytics-dashboard.md b/content/en-us/production/analytics/analytics-dashboard.md index b0c100d34..7c2c9b7fd 100644 --- a/content/en-us/production/analytics/analytics-dashboard.md +++ b/content/en-us/production/analytics/analytics-dashboard.md @@ -32,18 +32,18 @@ If you don't want to activate the dashboard immediately, or you accidentally dec ### Granting Group Permission -By default, for a [group experience](../../projects/groups.md), only the group owner with the "Create and edit group experiences" permission can view the analytics dashboard because some KPIs are sensitive information, such as your revenue. You can grant permission for your group members to access the analytics dashboard with the following steps: +By default in a [group experience](../../projects/groups.md), only the group **owner** can view the analytics dashboard, as some KPIs such as revenue are sensitive information. The owner can grant permission for group members to access the analytics dashboard as follows: 1. Select the group you want to grant permission on the [Groups](https://www.roblox.com/groups) page. - 2. Click the **⋯** button and select **Configure Group** in the dropdown menu. -3. Navigate to the **Roles** tab. Select an existing role that you want to grant access to the analytics dashboard or create a new role. +`--!native` from the more memory‑intensive scripts, allowing more smaller scripts to fit under the limit. Alternatively, move large or infrequently called functions to a separate non‑native module. +
+3. Navigate to the **Roles** tab. Select an existing role that you want to grant access to the analytics dashboard, or create a new role.
4. In the **Assets** section, toggle on **View group experience analytics**.
- 1. In the navigation menu, hover over **Revenue** to show the dropdown and then select **Sales**.
+ 2. Click the **⋯** button on the group banner and select **Configure Group**.
+ 3. In the navigation menu, hover over **Revenue** to show the dropdown and then select **Sales**.
+
+4. From the **Type of Transaction** dropdown, select **Sales of Goods**. Then click the **Download Data** button.
-1. From the **Type of Transaction** dropdown, select **Sales of Goods**. Then click the **Download Data** button.
-1. On the prompted calendar, select a calendar month of sales data to download. You can choose any month from the current date to up to two years ago. If you choose the current month, the file will include all available data of the partial month.
+
+5. On the prompted calendar, select a calendar month of sales data to download. You can choose any month from the current date to up to two years ago. If you choose the current month, the file will include all available data of the partial month.
+
-1. In your inbox of your verified email address, you receive an email with a link to download a `.zip` file that contains your sales data in `.csv` format. The link will expire after 48 hours.
-1. You can use the `.csv` sales data sheet to analyze the data in your desired way to meet your specific business needs. For example, you can filter to display only sale records with pending Robux to release to you, so you can calculate the timeline and amount of your sales payout to make decisions on when to [exchange earned Robux for real-world currency (DevEx)](../../production/earning-on-roblox.md#the-developer-exchange-program) or pay your collaborators.
+
+6. In your inbox of your verified email address, you receive an email with a link to download a `.zip` file that contains your sales data in `.csv` format. The link will expire after 48 hours.
+
+7. You can use the `.csv` sales data sheet to analyze the data in your desired way to meet your specific business needs. For example, you can filter to display only sale records with pending Robux to release to you, so you can calculate the timeline and amount of your sales payout to make decisions on when to [exchange earned Robux for real-world currency (DevEx)](../../production/earning-on-roblox.md#the-developer-exchange-program) or pay your collaborators.
### Sales Data Attributes
diff --git a/content/en-us/production/publishing/publishing-experiences-and-places.md b/content/en-us/production/publishing/publishing-experiences-and-places.md
index e8bf3f3c2..946ae883a 100644
--- a/content/en-us/production/publishing/publishing-experiences-and-places.md
+++ b/content/en-us/production/publishing/publishing-experiences-and-places.md
@@ -177,26 +177,26 @@ Roblox strongly recommends that you fill out the guidelines questionnaire for ea
### Allowing Copying
-By default, all private and public experiences are locked so that you or your group are the only creators who have access to edit its place files. However, if you want to allow other creators to be able to download an editable copy of your experience for their own creator process, you can **uncopylock** the experience. This is particularly helpful when you create templates or reference files for open use.
+By default, all private and public experiences are locked so that you or your [group](../../projects/groups.md) are the only creators who have permission to edit its place files. However, if you want to allow other creators to be able to access an editable copy of your experience for their own creation process, you can **uncopylock** the experience. This is particularly helpful when you create templates or reference files for open use.
-To allow users to download an editable copy of your experience:
+To allow the community to access an editable copy of your experience:
1. Navigate to the [Creator Dashboard][creatordashboard].
-1. Click on the thumbnail of the experience you want to allow users to copy. The experience's **Overview** page displays.
-1. In the left-hand navigation, under **Configure**, select **Places**.
+2. Click on the thumbnail of the experience you want to allow users to copy. The experience's **Overview** page displays.
+3. In the left-hand navigation, under **Configure**, select **Places**.
-1. Click the **start place** marked with a star icon. The place's **Basic Settings** page displays.
+4. Click the **start place** marked with a star icon. The place's **Basic Settings** page displays.
-1. In the place's left-hand navigation menu, select **Permissions**.
+5. In the place's left-hand navigation menu, select **Permissions**.
-1. Enable **Allow users to download a copy of this Place**.
-1. Click the **Save Changes** button. Your experience is now uncopylocked and creators can download an editable copy of it from the experience's main page.
+6. Enable **Allow users to download a copy of this Place**.
+7. Click the **Save Changes** button. Your experience is now uncopylocked and creators can access an editable copy of it from the experience's main page.
diff --git a/content/en-us/projects/collaboration.md b/content/en-us/projects/collaboration.md
index ca7c15f28..543e86a9e 100644
--- a/content/en-us/projects/collaboration.md
+++ b/content/en-us/projects/collaboration.md
@@ -14,53 +14,33 @@ With Studio's **built-in** **collaboration tools**, creators can contribute to e
Collaborators you add to an experience have permission settings that correspond to their level of access to the experience. As follows are the different user permission settings:
| **Permission** | -**Description** | -
|---|---|
| **Owner** | -User is the owner of the experience and has permission to configure other users' permissions. | -
| Permission | +Description | +
| **Owner** | +User is the owner of the experience and has permission to configure other users' permissions. | +
| **Edit** | -User has permission to edit the experience. This also grants the user **Play** permission. | -**Edit** | +User has permission to edit the experience. This also grants the user **Play** permission. | +
| **Play** | -User has permission to play the experience privately. | -**Play** | +User has permission to play the experience privately. | +
| **No Access** | -User does not have either **Edit** or **Play** permissions. | -**No Access** | +User does not have either **Edit** or **Play** permissions. | +
-
-1. Type into the search bar at the top to search for a collaborator to add. A dropdown appears listing matching collaborators, with friends indicated by the **Friend** label below their name. Select the collaborator to add.
-
- 
-
-1. Select **Edit** from the permissions dropdown for the friend.
-
- 
-
-1. Click **Save** for your collaboration settings to take effect.
+There are some small differences when managing collaborators in [group‑owned experiences](#group-owned-experiences) vs. [user‑owned experiences](#user-owned-experiences).
### Group-Owned Experiences
@@ -73,18 +53,21 @@ If you're the group's owner, you can set permissions across **all** group experi
1. Navigate to the [Groups](https://www.roblox.com/groups) page and select the group.
1. Click the **⋯** button in the upper-right corner and select **Configure Group**.
- 
+
1. In the left column of the group configuration page, select the **Roles** tab.
+
+ 
+
1. Select each group role that you want to give editing permission to and enable **Create and edit group experiences**.
- 
+
In Studio's **Manage Collaborators** window for any group-owned experience, these roles display **Edit** permission but are muted to indicate that you can't change the permission level from Studio.
- 
+
+
1. Click **Save** for your collaboration settings to take effect. All group members within the modified roles should now have **Edit** permission for this experience only; this action won't grant them equal permission to other group experiences.
+
+1. Type into the search bar at the top to search for a collaborator to add. A dropdown appears listing matching collaborators, with friends indicated by the **Friend** label below their name. Select the collaborator to add.
+
+
+
+1. Select **Edit** from the permissions dropdown for the friend.
+
+
+
+1. Click **Save** for your collaboration settings to take effect.
+
## Accessing a Session
Those who have permission to edit an experience can join a collaborative session as follows:
-1. Close all currently open places in Studio, or restart Studio.
-1. Select the **Group Games** tab if it's a [group-owned](../projects/groups.md) experience, or the **Shared With Me** tab for a user-owned experience.
+1. Navigate to the [Creator Dashboard](https://create.roblox.com/dashboard/creations).
+1. Locate the experience depending on whether it's [group-owned](#group-owned-experiences) or [user-owned](#user-owned-experiences).
+
+ 
+
+ 
+ 
-1. Click the desired tile to begin editing.
+ 
### Viewing Collaborators
While working in a collaborative session, you can see the current collaborators in the upper-right corner of Studio, each with a unique assigned color that's consistent across all collaborators' devices.
-
+
-To view more details on the current collaborators, click on any of the icons to open the **Live Collaborators** window. In this window, you can see:
+To view more details on the current collaborators, click on any of the icons to open the **Live Collaborators** window. In this window, you can see whether a user is active or inactive inside Studio, as well as an indication of where the user is working. Users become inactive if they do not use Studio for more than 5 minutes.
-- **Collaborator Status** — Whether a collaborator is active or inactive inside Studio. Users become inactive if they do not use Studio for more than 5 minutes.
-- **Collaborator Location** — Short description of where the user is working, such as in the 3D workspace or inside a specific script file.
-
-
+
### Selection Visualization
@@ -162,82 +177,99 @@ To chat with collaborators during a session:
## Collaborative Scripting
-If a collaborative session, Roblox stores scripts in a central cloud-based repository that all collaborators can access. This allows them to:
+In a collaborative session, you can code together in real-time through [live scripting](#live-scripting), or you can [draft](#drafts-mode) scripts in a more focused environment before committing them to a collaborator‑shared repository.
-- Work on the same script that others are editing using drafts.
-- Test changes locally before committing them to the cloud.
-- Compare and commit script changes to the cloud when ready.
+### Live Scripting
+
+
+### Drafts Mode
-
+Through **Drafts** mode, you can independently edit and test scripts without affecting the experience for others. After you finish drafting a script, you can [commit](#committing-drafts) it to the shared repository and [Team Test](../studio/home-tab.md#team-test) the committed version with collaborators.
-### Comparing Local and Cloud Scripts
+
+Once you've edited a script, it appears in the **Drafts** window, accessible from the [View](../studio/view-tab.md) tab. Drafts are saved to your local file system and persist between Studio sessions on the same machine.
-1. Compare the line numbers to help determine which to keep. Code that collaborators changed or deleted appears in red. Code that you updated appears in green.
+
- 
+
-### Committing Scripts to the Cloud
+To commit your local edits to the repository, left-click a script, or hold Shift and left-click to select multiple scripts. Then click **Commit** to commit all selected scripts.
-To commit your local edits to the cloud:
+
-1. Left-click a script, or hold Shift and left-click to select multiple scripts.
-1. Click **Commit** to commit all selected scripts to the cloud.
+#### Comparing and Merging Changes
-
+If another collaborator commits changes to the same script that you're editing, an icon with a green **⊕** symbol appears in the **Drafts** window. To view their changes, right‑click the script and select **Compare With Server**.
-### Merging Changes
+
-If a collaborator commits to the same script that you're editing, an icon with a green ⊕ symbol appears in the **Drafts** window.
+In the **(Diff)** tab that opens in the [Script Editor](../studio/script-editor.md), code that other collaborators changed or deleted appears in red, while code that you updated appears in green.
-
+
To merge their changes into your script:
-1. Identify which scripts you need to merge.
-1. Left-click a script, or hold Shift and left-click to select multiple scripts.
-1. Right-click any selected script.
-1. Click **Merge from server** to open the **Merge Tools** window. This window shows you how the latest edits relate to your own. If there are conflicting changes, you can pick which code to keep, or make manual edits.
+1. In the **Drafts** window, right‑click the script and select **Merge From Server**.
+
+ 
+
+1. In the merge window, you can pick which code to keep, or make manual edits.
+
+ - Check **Draft** to keep your changes, or leave it unchecked to discard them.
+ - Check **Server** to merge the committed changes into your draft, or leave it unchecked to ignore them.
+ - Check **Other** to manually edit the script and save the changes to your draft.
+
+1. Once you've previewed the merge resolution, click **Merge All** to update your local script.
- - Select **Draft** to keep your changes or leave it unchecked to discard them.
- - Select **Server** to merge the changes into your draft or leave it unchecked to ignore them.
- - Select **Other** to manually edit the script and save the changes to your draft.
+#### Restoring Deleted Scripts
-1. Once you check the desired options, toggle the **Preview Resolution** switch to preview how the script will look.
+If a collaborator deletes a script that you're editing, an icon with a red **⊘** symbol appears in the **Drafts** window. To restore the script, right‑click it and select **Restore Script**. Scripts are restored to the place's **Workspace** tree, so you may need to manually re‑parent them back to their original location.
- 
+
-### Restoring Deleted Scripts
+### Viewing Script History
-If a collaborator deletes a script that you're editing, an icon with a red ⊘ symbol appears in the **Drafts** window:
+All script changes, whether saved by a collaborator, auto-saved, or committed by a collaborator through [Drafts](#drafts-mode) mode, are logged in the **Version History** window. To access it:
-
+1. Right-click the script in the [Explorer](../studio/explorer.md) window and select **View Script History**.
+2. In the **Version History** window that opens, you'll see all committed versions of the script, the commit date, which collaborator committed, and more. From this window, the following actions are possible:
-To restore deleted scripts:
+
+
1. In the left column, select the **Roles** tab.
-
-
-1. To secure your group and its creations, inspect and adjust the permissions for each role.
-
-| Posts | -|
|---|---|
| View group wall | -View discussions on the group's wall. | -
| Post on group wall | -Participate in conversations on the group's wall. | -
| Delete group wall posts | -Delete posts that other members have made on the group's wall. | -
| View group shout | -See the group status. | -
| Post group shout | -Update the group status. | -
| Members | -|
| Manage lower-ranked member ranks | -Change the role of other members currently assigned to a lower-ranked role. | -
| Accept join requests | -Accept or deny any pending requests to join the group, assuming the group is currently set to require manual approval. | -
| Kick lower-ranked members | -Kick out members assigned to lower-ranked roles. | -
| Miscellaneous | -|
| Manage allies and enemies | -Declare or remove 'ally' and 'enemy' groups that display on the group's profile. | -
| View audit log | -Monitor changes regarding the group. | -
| Assets | -|
| Spend group funds | -Use the group's funds for certain group-related actions. | -
| Advertise the group | -Create ads for the group via the Advertise Group menu option. | -
| Create group items | -Create group items via the Store tab on the group's main page. | -
| Configure group items | -Manage existing items via the Store tab on the group's main page. | -
| Create and edit group experiences | -Create and edit experiences and assets that are specifically owned by the group. | -
| View group experience analytics | -View analytics for group experiences. | -
| Open Cloud | -|
| Create group API keys | -Create and view API keys for this role, but not manage keys for other roles. | -
| Administer all group API keys | -Gain all of the permissions that a group owner has for API keys, including the ability to create, view, edit, revoke, and audit all of the group's keys. | -
+
+1. To secure your group and its creations, inspect and adjust the permissions for each role. Commonly managed options include:
+
+ | Members | +|
|---|---|
| **Manage lower‑ranked member ranks** | +Change the role of other members currently assigned to a lower‑ranked role. | +
| **Accept join requests** | +Accept or deny any pending requests to join the group, assuming the group is currently set to require manual approval. | +
| **Kick lower‑ranked members** | +Kick out members assigned to lower‑ranked roles. | +
| Assets | +|
| **Spend group funds** | +Use the group's funds for certain group‑related actions. | +
| **Create and edit group experiences** | +Create and edit experiences and assets that are specifically owned by the group. See [here](../projects/collaboration.md#group-owned-experiences) for how this setting relates to collaborative sessions. | +
| **View group experience analytics** | +View analytics for group experiences. See [here](../production/analytics/analytics-dashboard.md#granting-group-permission) for details. | +
-## Publishing Group Places
-
-If you're the group owner or a member with the **Create and edit group experiences** permission, you can publish a group place as follows.
-
-### New Experience
-
-1. In Studio, select **File** → **Publish to Roblox**.
-1. Near the bottom of the window, click **Create new game**.
-1. Enter a place name and an optional description.
-1. For the **Creator** field, select the group for which you'd like to publish the place.
-1. When ready, click the **Create** button.
-
-### To Existing Experience
-
-1. Select **File** → **Publish to Roblox**.
-1. Select a group from the drop-down menu.
-1. Click an existing group experience. On the next screen you can:
-
- - Add the place you're publishing as a **new** place within the same experience.
- - Overwrite an existing place within the experience.
-
-1. Click the **Create** or **Overwrite** button.
-
## Managing Payouts
You can use groups to share Robux revenue. Group owners can pay contributors by either transferring group funds as a one-time payout or by scheduling recurring payouts. Roblox monitors payouts to prevent fraud and abuse.
@@ -190,51 +98,52 @@ You can use groups to share Robux revenue. Group owners can pay contributors by
To manage payouts:
1. Navigate to the [Groups](https://www.roblox.com/groups) page and select your group.
-1. Click the **…** button in the upper-right corner and select **Configure Group**.
+1. Click the **⋯** button in the upper-right corner and select **Configure Group**.
-
+
1. In the left column, hover over **Revenue** and then click **Payouts**.
- 
-
-### One-Time Payouts
-
-Group owners can perform one-time payouts of Robux to a single group member or multiple members. This payout can be a lump sum or a percentage of the group's total funds, but you can only distribute Robux in whole numbers. If you choose to distribute by percentage, the amount rounds down to the nearest whole number of Robux, and the remainder remains in the group's funds.
-
-To transfer a one-time payout:
-
-1. Select the **One-time Payout** tab.
+
- 
+ From the payouts screen, initiate a **recurring payout** or **one‑time payout**.
-1. Use the drop-down menu to choose whether the payout is a set amount or a percentage of the group's total Robux balance.
+ 
-### Recurring Payouts
+ 2. Add one or more payout recipients by clicking the **Add Payout Recipient** button.
+ 3. Next to each member, enter the percentage of the group's Robux that you would like them to receive every month. To remove them from the payout, click the "trash" button.
+ 4. After everything looks correct, click **Save**.
-Group owners can configure recurring payouts to automatically share profits when the group earns them. There's a short delay from when the group earns the funds and when they distribute to members. When you change a member's recurring payout, Roblox sends a message notification to that member to inform them of the change.
+
+
-1. Add one or more payout recipients by clicking the **Add Payout Recipient** button.
-1. Next to each member, enter the percentage of the group's Robux that you would like them to receive every month. To remove them from the payout, click the "trash" button.
+ 2. Use the drop-down menu to choose whether the payout is a set amount or a percentage of the group's total Robux balance.
+ 3. Add one or more payout recipients by clicking the **Add Payout Recipient** button.
+ 4. Next to each member, enter the amount or percentage you want to give to them. To remove them from the payout, click the "trash" button.
+ 5. After everything looks correct, click **Distribute**.
-1. After everything looks correct, click **Save**.
+ Class.DecalClass.Decal.Texture