> For the complete documentation index, see [llms.txt](https://sl-scritps.gitbook.io/sl-scripts-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sl-scritps.gitbook.io/sl-scripts-documentation/products/sl-dev-pose-lab.md). # SL Dev Pose Lab ## SL Dev Pose Lab **Code:** DPL-54\ **Resource:** `sl_dev_pose_lab`\ **Version:** v0.3.14\ **Category:** Developer Tool / Admin Tool / Pose & Scene Utility\ **Status:** Stable **Structured tools for serious roleplay servers.** *** ### Overview SL Dev Pose Lab is a developer and creator tool for FiveM servers. It helps admins, developers, content creators and staff test animations, poses, actors, props, offsets, camera angles and scene composition directly in game. The resource is designed to make development, QA, screenshots, promotional media and scene building easier without constantly editing code manually. *** ### What is this script for? SL Dev Pose Lab gives server owners and creators a visual testing space for roleplay content. It is useful for: * Testing animations * Testing pose offsets * Previewing props * Creating scene references * Testing actor positions * Preparing screenshots * Building promotional images * Designing RP scenes * Checking emote compatibility * Adjusting camera angles * Creating reference layouts for other scripts * Supporting staff and dev QA The main goal is: ```txt Open the pose lab → test actors/props/animations → adjust scene → use the result as reference ``` *** ### Roleplay Experience SL Dev Pose Lab is mainly an OOC creator/admin tool. Normal players usually do not need to use it directly. Instead, players benefit from the final result: ```txt Better screenshots Cleaner scenes Improved animations Better prop placement More polished RP content More consistent event setups ``` The tool helps staff and developers prepare content that later feels better inside the IC world. *** ### Player IC Usage SL Dev Pose Lab is not usually a normal player-facing activity. Players may experience content created or tested with it, such as: * A better positioned prop * A cleaner animation * A cinematic event setup * A staff-created scene * A screenshot location * A roleplay pose reference * A promotional scene for the server From the player perspective, the result should feel natural. Example: ```txt A player enters an event area. The props, actors and poses look properly placed. The scene feels intentional and polished. ``` Players do not need to know that the setup was tested in Dev Pose Lab. *** ### Creator / Admin IC Usage For admins, staff and creators, SL Dev Pose Lab supports worldbuilding and visual preparation. Even though the tool is technical, it helps create better IC spaces and scenes. Common creator/admin IC uses: * Prepare a staged RP scene * Build a screenshot composition * Test an NPC pose for an event * Align props around an actor * Create a reference for a scripted interaction * Prepare a cinematic intro or outro * Test an animation before adding it to another resource * Adjust a scene before players arrive Example creator flow: ```txt Choose location → add actor → apply animation → add prop → adjust offsets → test camera → save/use reference ``` Example admin/event use: ```txt Staff prepares a news interview scene. They spawn an actor, test a standing pose, add a microphone prop and adjust the camera. The final scene is used as reference for the event. ``` *** ### Admin / Developer Technical Flow SL Dev Pose Lab is mainly used by admins, developers, staff and trusted creators. Common technical actions may include: * Open the Dev Pose Lab panel * Spawn or select an actor * Apply an animation * Adjust actor position * Adjust rotation * Attach or preview props * Move props with offsets * Use free camera * Test reference scale * Preview overlays * Export or copy values * Use the scene as a reference for another script * Clean up test actors and props Recommended testing flow: ```txt 1. Open Dev Pose Lab. 2. Spawn or select an actor. 3. Apply a test animation. 4. Add a prop if needed. 5. Adjust position and rotation. 6. Test camera view. 7. Confirm the pose looks correct. 8. Copy/export reference values if needed. 9. Clean up spawned actors and props. ``` *** ### Example Use Cases #### Animation testing A developer wants to test if an animation looks good for a script. ```txt Open Pose Lab → select actor → play animation → adjust position → confirm result ``` *** #### Prop offset testing A creator wants to attach a prop correctly to a character. ```txt Spawn actor → attach prop → adjust offset → test different angles → copy final values ``` *** #### Screenshot scene A staff member prepares a promotional screenshot. ```txt Place actors → apply poses → adjust props → use free camera → capture image ``` *** #### Event preparation Admins prepare a scene before players arrive. ```txt Test actor placement → check camera angle → confirm props → recreate final setup in event ``` *** #### Script development reference A developer uses Dev Pose Lab to find good values for another resource. ```txt Test pose → copy coordinates/rotation/offset → apply values in script config ``` *** ### What this resource is not SL Dev Pose Lab is not intended to be a normal public roleplay activity for every player. It is focused on: ```txt development animation testing pose testing prop offsets actor preview camera reference scene composition creator workflow ``` It is a tool for improving other content, not a replacement for a full emote menu, cinematic recorder or mission system. *** ### Main Features * Pose and animation testing * Actor tools * Prop preview tools * Prop offset testing * Multi-actor support * Free camera support * Reference scale tools * Overlay preview support * Scene composition workflow * Position and rotation adjustment * Developer-friendly testing panel * Useful for screenshots and promotional scenes * Useful for QA and animation checks * Clean SL Scripts style * Admin/creator-oriented workflow *** ### Dependencies #### Required ```txt FiveM server ``` #### Recommended / Optional ```txt ox_lib QBCore Qbox ESX Standalone mode ``` The exact dependency setup depends on server configuration. Because this is mainly a developer/admin tool, it can often be used without complex economy, inventory or database systems. *** ### Installation Notes 1. Place the resource folder inside your server resources folder. Example: ```txt resources/[sl_scripts]/sl_dev_pose_lab ``` 2. Make sure the folder name is: ```txt sl_dev_pose_lab ``` 3. Configure: ```txt config.lua custom.lua locales/ ``` 4. Add the resource to your `server.cfg`. Example: ```cfg ensure ox_lib ensure sl_dev_pose_lab ``` If your build does not require `ox_lib`, configure the fallback mode in `config.lua`. *** ### How to Use #### Basic Creator Flow 1. Open the Dev Pose Lab panel. 2. Select or spawn an actor. 3. Choose an animation or pose. 4. Adjust the actor position and rotation. 5. Add props if needed. 6. Adjust prop offsets. 7. Use the camera tools to inspect the scene. 8. Copy or use the final values as reference. 9. Clean up the test scene when finished. #### IC / RP Output Summary ```txt Creator prepares scene → content is tested → final RP scene looks cleaner ``` #### OOC / Technical Summary ```txt Panel opens → actor/prop/animation selected → offsets adjusted → values tested/exported → cleanup ``` *** ### Controls Exact controls may depend on configuration, but common tool behavior may include: ```txt WASD = move camera or controlled element Mouse = look / camera movement Scroll = adjust distance or rotation depending on mode ENTER = confirm BACKSPACE / ESC = cancel or exit SPACE = toggle helper/HUD depending on mode ``` Check `config.lua` and in-game hints for the exact control layout. *** ### Commands Command names may depend on configuration. Common command examples: ```txt /poselab /devposelab /sl_poselab ``` Possible helper commands: ```txt /poselab_cleanup /poselab_reset ``` Check `config.lua` for the exact command names used by your installed version. Commands are mainly intended for admins, developers and trusted creators. *** ### Permissions SL Dev Pose Lab should normally be restricted. Recommended access logic: ```txt Players = no direct access by default Trusted creators = use pose lab Staff = use pose lab for events/screenshots Admins = full access Owners = full access ``` Permissions may use: * Ace permissions * Framework groups * Config admin list * Custom permission bridge Recommended: ```txt Do not give this tool to all players on a live server. ``` The tool can spawn actors, props or camera states depending on configuration, so access should be controlled. *** ### Configuration Open: ```txt config.lua ``` Common settings may include: ```txt Product information Locale Debug mode Startup logs Command settings Permission settings Actor settings Animation settings Prop settings Camera settings Overlay settings Reference scale settings Cleanup settings UI settings ``` Recommended for production: ```lua Config.Debug = false ``` Use debug mode only while testing or troubleshooting. *** ### Custom Integrations Open: ```txt custom.lua ``` Use this file for server-specific functions such as: * Custom notifications * Custom permission checks * Custom framework integration * Custom admin checks * Custom logging * Custom creator access If your server uses standard admin groups, you may only need to configure permissions. *** ### Startup Logs When the resource starts correctly, you may see logs similar to: ```txt [sl_dev_pose_lab][INFO] Server ready: SL Dev Pose Lab v0.3.14 [sl_dev_pose_lab][INFO] Client ready: SL Dev Pose Lab v0.3.14 | Use /poselab ``` If startup logs are disabled, check `config.lua`. *** ### Best Practices #### Use it on a test server first SL Dev Pose Lab is safest when used on a development or staging server. Recommended: ```txt Test animations and props in a controlled environment before using them live. ``` *** #### Clean up after testing After using actors, props or test scenes, always clean up. Recommended: ```txt Do not leave test peds or props active in public areas. ``` *** #### Save useful values When you find a good pose, prop offset or camera angle, save the values for later use. Useful for: * Config files * Other scripts * Event notes * Documentation * Screenshots * QA reports *** #### Keep access limited Only trusted staff should use Dev Pose Lab on a live server. This avoids: * Prop spam * Accidental scene clutter * Confusing players * Unwanted camera/tool usage * Performance issues from test entities *** ### Troubleshooting #### The panel does not open Check: ```txt - The resource is started. - You are using the correct command. - You have permission to use the tool. - NUI files exist if the panel uses NUI. - F8 console has no JavaScript errors. - Server console has no permission/config errors. ``` *** #### Actor does not spawn Check: ```txt - Actor tools are enabled. - The ped model exists. - The model name is correct. - Spawn location is valid. - Client F8 console has no model loading errors. ``` *** #### Animation does not play Check: ```txt - Animation dictionary is valid. - Animation name is valid. - The animation is loaded correctly. - The actor is valid. - Another task is not interrupting the animation. - F8 console has no animation errors. ``` *** #### Prop does not appear Check: ```txt - Prop tools are enabled. - The prop model exists. - The model name is correct. - The model loads successfully. - You are within streaming distance. - F8 console has no model loading errors. ``` *** #### Prop offset looks wrong Check: ```txt - Correct bone is selected if bone attachment is used. - Offset values are being applied in the correct axis. - Rotation order is correct. - Actor animation is active while testing. - Prop is attached to the expected actor. ``` *** #### Free camera feels stuck Check: ```txt - Free camera mode is enabled. - Another camera resource is not active. - NUI focus is not blocking controls. - You are using the correct movement keys. - Reset the camera if needed. ``` *** #### Scene stays after closing the tool Check: ```txt - Cleanup option is enabled. - Manual cleanup command is available. - Actors/props were spawned by the tool. - Another resource did not take ownership of the entity. ``` Try the configured cleanup/reset command. *** #### Normal players can open the tool Check: ```txt - Permission settings. - Ace permissions. - Framework group detection. - custom.lua permission bridge. - Config admin list. ``` Recommended: ```txt Restrict Dev Pose Lab to admins, owners, staff and trusted creators. ``` *** ### Version Notes #### v0.3.14 * Stable Dev Pose Lab workflow. * Status, actor, animation and prop sections available. * Free camera supported. * Reference scale tools improved. * Overlay preview supported. * Multi-actor workflow supported. * Useful for scene composition, screenshots and development reference. #### v0.3.x * Continued pose, actor and prop testing improvements. * UI and workflow refined for creator use. * Camera and reference tools improved through testing. *** ### Support When asking for support, include: ```txt Product: SL Dev Pose Lab Resource name: sl_dev_pose_lab Version: Framework: Issue: Steps to reproduce: Command used: Actor model: Animation dictionary/name: Prop model: Server console error: Client F8 error: Screenshot/video: ``` Example: ```txt Product: SL Dev Pose Lab Resource name: sl_dev_pose_lab Version: v0.3.14 Framework: Qbox Issue: Prop appears but offset does not match the actor hand Steps to reproduce: Open /poselab, spawn actor, apply animation, attach prop Command used: /poselab Actor model: mp_m_freemode_01 Animation dictionary/name: attached Prop model: attached Server console error: none Client F8 error: none Screenshot/video: attached ``` *** ### Final Notes SL Dev Pose Lab works best as a trusted creator and developer tool. For best results, use it to test animations, props, actors and camera compositions before applying final values to live scripts, events or public RP scenes. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://sl-scritps.gitbook.io/sl-scripts-documentation/products/sl-dev-pose-lab.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.