SCROOMS Developers and official links

Identify what each source actually establishes

The Roblox group API names RomanDevX as the group owner. Doni identifies himself as one of the owners in the Interlude preview. These are separately described statements, not a complete organization chart. The research does not establish every team role, and this fan reference does not represent the developers or provide account support on their behalf.

Official sources can still be single-source evidence

An official publisher is a useful source for its own announcement or API field. Several endpoints from that publisher are not independent confirmation. For example, the Undergarden event listing supplies the exact time window, while the preview describes planned content. The event record keeps the precise-time label separate from confidence that the event exists.

• Undergarden announcement record

Understand the Discord boundary

The public invitation metadata identifies the Discord destination. It does not reveal private announcement messages or update logs. The supplied research did not read those channels, so the fieldbook does not reconstruct their contents. Following a Discord or Roblox link is an outbound navigation; the site does not embed either service or contact it while rendering a page.

Separate community accounts from official channels

The release announcement used here came through the community lead’s personal X account. That source is labelled as a player post in the site data, rather than being promoted to an official game account. No official wiki or Trello was identified in the research. The source register describes guide websites as independent references.

• Public release evidence
• Source register and publisher types

What is still unknown

The snapshot does not contain accessible private patch notes, a verified official game X account or a complete developer contact directory. A directly identified public announcement would be needed to add one. The fieldbook’s contact address is for this reference site; it is not presented as a route to the SCROOMS development team.

• Contact the fieldbook