> 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-photo-mode.md). # SL Photo Mode ## SL Photo Mode **Code:** PHO-51\ **Resource:** `sl_photomode`\ **Version:** Current Release\ **Category:** Camera Tool / Screenshot Tool / Cinematic Utility\ **Status:** Stable **Structured tools for serious roleplay servers.** *** ### Overview SL Photo Mode is a photo mode and cinematic camera tool for FiveM roleplay servers. It allows players, staff and creators to capture cleaner screenshots, frame roleplay moments, prepare promotional media and use camera controls in a more polished way than a normal gameplay camera. The resource is designed for servers that want better visual content, screenshots and cinematic presentation without relying only on external tools. *** ### What is this script for? SL Photo Mode gives servers a dedicated camera experience for screenshots and visual roleplay. It is useful for: * Player screenshots * Character photography * Vehicle photography * Business promotion * Event coverage * Social media content * Server marketing * Staff screenshots * Cinematic RP moments * News/media roleplay * Creator and community content The main goal is: ```txt Open photo mode → control camera → frame the scene → capture the moment ``` *** ### Roleplay Experience SL Photo Mode can be used in both IC and OOC ways. In IC, it can support roleplay where a character is taking photos, covering an event, documenting a scene or creating visual content. In OOC, it can help staff, owners and creators capture better screenshots for announcements, Tebex pages, Discord posts, trailers or documentation. The resource works best when it feels like a clean camera tool, not a distracting admin menu. *** ### Player IC Usage For players, SL Photo Mode can support character-based photography and social roleplay. Common player IC uses: * Taking photos with friends * Capturing vehicle meets * Covering business openings * Taking event photos * Creating memories from RP moments * Playing as a photographer * Playing as a journalist or media worker * Documenting scenes for RP purposes Normal player flow: ```txt Open photo mode → position camera → frame subject → take screenshot → continue RP ``` Example IC lines: ```txt “Hold still, I’m taking a photo.” “This will look good for the event post.” “Let me get a better angle.” “I’ll take some photos for the business page.” ``` Photo Mode works best when players use it to support the scene instead of interrupting the flow of roleplay. *** ### Photographer / Media IC Usage For photographer, journalist or media-style characters, SL Photo Mode can become part of their IC job. Common IC actions: * Take photos at events * Cover public scenes * Photograph businesses * Create promotional images * Capture vehicle showcases * Document community moments * Support news/media RP * Take staged portraits Example IC flow: ```txt Arrive at scene → ask for permission or position → frame photo → capture → share result through server channels ``` Example IC lines: ```txt “I’m here to cover the event.” “Can I get one photo in front of the sign?” “This angle shows the whole crowd.” “I’ll send the photos after the event.” ``` This makes the tool useful for servers that want stronger media, photography or creator roleplay. *** ### Player / IC Flow #### 1. The player opens Photo Mode Depending on configuration, the player may open Photo Mode with a command, keybind or allowed interaction. Common command examples: ```txt /photomode /photo ``` Check your configuration for the exact command. *** #### 2. The player controls the camera Once Photo Mode is active, the player can move or adjust the camera depending on the configured controls. Common camera actions may include: ```txt move camera rotate camera zoom change height adjust angle toggle UI reset camera exit photo mode ``` The exact controls depend on configuration. *** #### 3. The player frames the scene The player positions the camera around a character, vehicle, prop, business or event. Good use cases: ```txt portraits group photos vehicle photos event photos business photos cinematic screenshots ``` *** #### 4. The player captures the image The actual screenshot capture may depend on the player’s screenshot tool, FiveM settings or server/community workflow. Common capture methods may include: ```txt FiveM screenshot tools Steam screenshot Windows screenshot third-party recording/screenshot software server screenshot workflow if configured ``` SL Photo Mode helps frame the image; the final capture method may depend on the user setup. *** #### 5. The player exits Photo Mode When finished, the player exits Photo Mode and returns to normal gameplay. Expected result: ```txt Camera returns to normal. Controls return to normal. The player continues roleplay. ``` *** ### Admin / Owner IC Usage For admins, owners and staff, SL Photo Mode can be used to improve server presentation and event documentation. Common admin/owner IC or event uses: * Capture official event photos * Create Discord announcement images * Take screenshots for Tebex * Document server updates * Photograph new locations * Capture business openings * Prepare cinematic media * Support news/media staff * Create promotional images for SL Scripts-style resources or server content Example admin/event flow: ```txt Prepare location → gather players/props → open Photo Mode → capture angles → publish screenshots ``` Example event scenario: ```txt Staff hosts a city event. A photographer uses Photo Mode to capture crowd shots, business booths and key moments. The images are later posted in Discord as event memories. ``` For server owners, this can improve how the server looks publicly. *** ### Admin / Owner Technical Flow Admins and owners should configure access, controls and safe usage before enabling the tool publicly. Common admin actions may include: * Configure command names * Configure keybinds * Configure permissions * Configure camera limits * Configure distance limits * Configure UI visibility * Configure controls * Configure safe exit behavior * Configure whether players can use it freely * Test Photo Mode in public and private areas * Restrict use during serious RP if needed Recommended admin checks: ```txt 1. Confirm the resource starts correctly. 2. Open Photo Mode with the configured command. 3. Test camera movement. 4. Test zoom and rotation. 5. Test UI hide/show if available. 6. Test exit/reset behavior. 7. Confirm controls return after exiting. 8. Test permission restrictions. 9. Check F8 and server console for errors. ``` *** ### Example IC Scenarios #### Character photoshoot A player takes photos of their character or friends. ```txt “Stand near the car, this angle looks good.” ``` #### Vehicle meet Players gather at a vehicle meet and use Photo Mode for better screenshots. ```txt “Line the cars up for a photo.” ``` #### Business opening A business owner takes promotional images. ```txt “We need photos for the grand opening.” ``` #### News coverage A media roleplay character covers an event. ```txt “I’m taking photos for the article.” ``` #### Staff event documentation Staff captures screenshots during a server event. ```txt “These will be posted after the event.” ``` *** ### What this resource is not SL Photo Mode is not intended to replace a full video editor, cinematic recorder or professional external capture tool. It is focused on: ```txt camera control screenshot framing cinematic angles photo roleplay visual content support clean camera workflow ``` For trailers or advanced video editing, Photo Mode can be used together with recording/editing software. *** ### Main Features * Photo mode camera tool * Free camera-style movement depending on configuration * Cinematic screenshot support * Clean camera workflow * Player and staff use cases * Useful for character, vehicle and event screenshots * UI hide/show behavior when configured * Command or keybind access depending on configuration * Configurable permissions * Configurable camera limits * Configurable controls * Safe exit/reset behavior * Useful for media RP and server marketing * Clean SL Scripts style *** ### Dependencies #### Required ```txt FiveM server ``` #### Recommended / Optional ```txt ox_lib QBCore Qbox ESX Standalone mode ``` The exact dependency setup depends on server configuration. Photo Mode usually does not require inventory, target or database systems unless your installed version or custom configuration adds them. *** ### Installation Notes 1. Place the resource folder inside your server resources folder. Example: ```txt resources/[sl_scripts]/sl_photomode ``` 2. Make sure the folder name is: ```txt sl_photomode ``` 3. Configure: ```txt config.lua custom.lua locales/ ``` 4. Add the resource to your `server.cfg`. Example: ```cfg ensure ox_lib ensure sl_photomode ``` If your build does not require `ox_lib`, configure fallback behavior in `config.lua`. *** ### How to Use #### Basic Player Flow 1. The player opens Photo Mode. 2. The camera controls become available. 3. The player frames the subject. 4. The player hides UI if needed. 5. The player captures the screenshot with their chosen screenshot method. 6. The player exits Photo Mode. #### Basic Admin Flow 1. Admin confirms access and permissions. 2. Admin tests camera controls. 3. Admin captures official screenshots or event images. 4. Admin exits Photo Mode and confirms gameplay controls return normally. #### IC Summary ```txt Photographer opens camera → frames scene → captures moment → continues RP ``` #### OOC / Technical Summary ```txt Command/keybind opens tool → camera mode activates → player adjusts view → screenshot captured externally → camera resets ``` *** ### Controls Exact controls may depend on configuration. Common Photo Mode controls may include: ```txt W / A / S / D = move camera Mouse = look around Scroll = zoom or adjust camera distance Q / E = move camera down/up or rotate depending on mode SHIFT = faster movement CTRL = slower movement H = hide/show UI if configured ENTER = confirm or capture helper if configured BACKSPACE / ESC = exit Photo Mode ``` Check `config.lua` and in-game hints for the exact control layout. Recommended: ```txt Keep controls simple and show clear hints while Photo Mode is active. ``` *** ### Commands Command names may depend on configuration. Common command examples: ```txt /photomode /photo /sl_photo /sl_photomode ``` Possible admin command examples: ```txt /sl_photomode_admin /photoreset ``` Check `config.lua` for the exact command names used by your installed version. Commands are useful for opening Photo Mode, testing camera behavior or resetting the camera if needed. *** ### Permissions Permission setup depends on server configuration. Common permission levels may include: ```txt view use admin owner ``` Recommended access logic: ```txt Players = use Photo Mode if the server allows public photography Media jobs = use Photo Mode for IC photography/news Staff = use for events and documentation Admins = full access and reset tools Owners = full access ``` Permissions may use: * Ace permissions * Framework groups * Jobs * Job grades * Config admin list * Custom permission bridge Recommended: ```txt If Photo Mode can move the camera freely, restrict advanced camera access if your server needs tighter RP control. ``` *** ### Usage Guidelines #### Good uses ```txt screenshots event documentation character portraits vehicle photos business promotion server marketing news/media RP creator content ``` #### Avoid ```txt using camera to spy through walls interrupting serious RP blocking scenes while taking photos using Photo Mode during combat using camera access to gain unfair information staying in Photo Mode while others are waiting ``` Servers should define rules depending on how open or restricted they want Photo Mode to be. *** ### Configuration Open: ```txt config.lua ``` Common settings may include: ```txt Product information Locale Debug mode Startup logs Command settings Keybind settings Permission settings Camera speed Camera limits Zoom settings UI settings Control settings Exit/reset behavior Admin 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 job restrictions * Custom admin checks * Custom logging * Custom camera rules If your server uses standard permission systems, you may only need to configure access. *** ### Startup Logs When the resource starts correctly, you may see logs similar to: ```txt [sl_photomode][INFO] Server ready: SL Photo Mode [sl_photomode][INFO] Client ready: SL Photo Mode | Use /photomode ``` If startup logs are disabled, check `config.lua`. *** ### Best Practices #### Use Photo Mode for server identity Good screenshots help servers look more alive and professional. Recommended uses: ```txt Discord announcements Tebex images event recaps business promotion character showcases vehicle showcases ``` *** #### Keep RP flow respectful Photo Mode should support roleplay, not pause everyone around the user. Recommended: ```txt Ask people before staging long photos. Do not interrupt active serious scenes. Use it quickly during live RP. Use staff/event control for large photoshoots. ``` *** #### Restrict advanced access if needed If your server is strict about camera freedom, limit Photo Mode access to staff, media jobs or trusted players. Recommended: ```txt Public server = basic access or media-job access Strict RP server = restricted access Creator/test server = open access ``` *** ### Troubleshooting #### Photo Mode does not open Check: ```txt - The resource is started. - You are using the correct command. - Commands are enabled in config.lua. - You have permission to use Photo Mode. - F8 console has no errors. - Server console has no errors. ``` *** #### Camera does not move Check: ```txt - Camera mode activated correctly. - Controls are configured. - Another NUI or camera resource is not blocking controls. - You are not in a restricted state. - F8 console has no camera/control errors. ``` *** #### Camera feels too fast or too slow Check: ```txt - Camera speed settings. - Slow/fast modifier settings. - Zoom/distance settings. - Control sensitivity. ``` Adjust movement gradually and test in game. *** #### Player gets stuck after exiting Photo Mode Check: ```txt - Exit/reset behavior is enabled. - ESC/BACKSPACE exit control is configured. - Camera reset function is working. - Player controls are restored after exit. - Another resource is not taking camera control. ``` Try the configured reset command if available. *** #### UI does not hide Check: ```txt - UI hide/show key is configured. - NUI callbacks are working if used. - Another UI is still visible. - F8 console has no JavaScript errors. ``` *** #### Black box or dark rectangle appears behind the UI Check: ```txt - html/body background is transparent. - #app or #root background is transparent. - No fullscreen wrapper has a solid black background. - Panel opacity is controlled with rgba instead of global opacity. ``` Recommended CSS pattern: ```css html, body, #app, #root { background: transparent !important; } ``` Avoid using `opacity` on the full UI container because it also fades text, icons and buttons. *** #### Screenshots look different from the game view Check: ```txt - Screenshot tool settings. - Game resolution. - Graphics settings. - Timecycle/visual mods. - UI visibility. - Camera FOV or zoom. ``` Photo Mode controls the camera view, but the final screenshot output can depend on the capture method. *** #### Normal players can access restricted camera tools Check: ```txt - Permission settings. - Ace permissions. - Framework group detection. - Job/grade restrictions. - custom.lua permission bridge. - Config admin list. ``` *** ### Version Notes #### Current Release * Photo Mode camera workflow for screenshots and cinematic framing. * Supports player, media, staff and creator use cases. * Focused on clean visual presentation and practical camera control. * Includes guidance for transparent NUI handling when applicable. *** ### Support When asking for support, include: ```txt Product: SL Photo Mode Resource name: sl_photomode Version: Framework: Issue: Steps to reproduce: Command used: Permission setup: Server console error: Client F8 error: Screenshot/video: ``` Example: ```txt Product: SL Photo Mode Resource name: sl_photomode Version: Current Release Framework: Qbox Issue: Photo Mode opens but camera does not move Steps to reproduce: Use /photomode, try WASD/mouse controls Command used: /photomode Permission setup: admin only Server console error: none Client F8 error: attached Screenshot/video: attached ``` *** ### Final Notes SL Photo Mode works best as a visual support tool for roleplay communities. For best results, use it for clean screenshots, event coverage, character photography, vehicle showcases, business promotion and server media content. --- # 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-photo-mode.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.