1. What do you want to achieve?
I’m trying to build a Rust⁺-inspired remote camera system for a horror game. The idea is to let players check simplified in-game camera feeds (like motion alerts, position markers, etc.) from an external website or app by sending data from Roblox to a backend using HttpService:PostAsync().
2. What is the issue?
Right now, I’m not sure how far this concept can go within Roblox’s limitations. Since we can’t stream live video, I’m exploring how much useful or creepy player-facing data I can push externally without breaking ToS or hitting rate limits. The goal is to give the illusion of real-time surveillance without actually needing video.
Here’s a rough concept of the idea:
- Cameras placed in-game (real or dummy Viewport setups).
- Position/motion/alert data gets collected and sent to a server.
- That server could render something like a schematic feed, heatmap, or basic icons on a floorplan.
This is more about abstraction than realism like low-res visuals, almost like LIDAR or top-down surveillance.
3. What solutions have you tried so far?
I’ve tested sending basic camera position and movement data via HttpService, and I’ve gotten that to log on a local server. Haven’t yet started rendering the data externally, but I plan to visualize it using a web interface. I’ve read through the Developer Hub, especially on rate limits and HttpService, but examples on this kind of use cases are rare.
More context
The system wouldn’t be used for anything super sensitive just letting players peek into game areas while they’re not actively in the session (like checking for movement or alerts). This could be used for tension in horror games or light companion app stuff in ARGs.
My questions:
- Anyone tried something similar with external visualization?
- Is there a smarter way to serialize and send lightweight data for this kind of system?
- Would this fall within Roblox’s API use rules, especially for companion apps?