{ "server": "Hyperfy", "title": "Hyperfy Discord - 2025-05-07", "date": 1746576000, "stats": { "totalMessages": 104, "totalUsers": 28 }, "categories": [ { "channelId": "994775534733115412", "channelName": "💻│developers", "summary": "# Discord Chat Analysis for 💻│developers\n\n## 1. Summary\nThe main technical discussion centered around app-to-app communication in Hyperfy. Valiant sought help implementing a race system comprising four apps (StartRace, RaceGate, FinishRace, and RaceManager) that need to communicate with each other. Ashxn provided a detailed explanation of two main communication methods: app.send()/app.on() for same-app communication across the network, and app.emit()/world.on() for inter-app communication. Ashxn clarified that world.emit() was deprecated and replaced by app.emit(). 0mka suggested exploring world.set and world.get as additional options. There was also a brief mention of Gaussian splats integration possibilities with PlayCanvas, and a question about VRM exports with blendshapes across multiple meshes in Blender. The chat concluded with Valiant reporting progress on the race system implementation.\n\n## 2. FAQ\nQ: How do I implement app-to-app communication for a race system with multiple apps? (asked by Valiant) A: Use app.send()/app.on() for same-app communication across network and app.emit()/world.on() for different-app communication (answered by Ashxn)\nQ: What replaced the deprecated world.emit()? (asked by Valiant) A: It was replaced by app.emit() because \"it is the app emitting an event to the world\" (answered by Ashxn)\nQ: Has anyone done anything to show Gaussian splats in v2 yet? (asked by hiroP) A: Not that I know of... That's going to be COOL AF (answered by Agent12)\nQ: What's the new quickstart installation link? (asked by emotionull) A: https://docs.hyperfy.xyz/welcome/quickstart/ (answered by maximus)\nQ: Has anyone been successful in exporting generated VRMs with blendshapes through Blender? (asked by lucii.io) A: I could have sworn blender VRM supported blendshapes on more than one mesh (answered by Ashxn)\n\n## 3. Help Interactions\nHelper: Ashxn | Helpee: Valiant | Context: Implementing app-to-app communication for a race system | Resolution: Explained two communication methods with code examples showing how to use app.send()/app.on() and app.emit()/world.on()\nHelper: 0mka | Helpee: Valiant | Context: Additional options for app-to-app communication | Resolution: Suggested exploring world.set and world.get functions and offered specific help\nHelper: maximus | Helpee: emotionull | Context: Looking for updated documentation link | Resolution: Provided the correct URL to the new documentation\n\n## 4. Action Items\nTechnical: Implement app-to-app communication for race system using both app.send()/app.on() and app.emit()/world.on() | Description: Create communication between StartRace, RaceGate, FinishRace and RaceManager apps | Mentioned By: Valiant\nTechnical: Explore integration of Gaussian splats with PlayCanvas for Hyperfy v2 | Description: Research PlayCanvas repositories for possible integration methods | Mentioned By: hiroP\nTechnical: Investigate VRM plugin modification for Blender | Description: Modify script to accommodate blendshapes on multiple meshes in VRM exports | Mentioned By: lucii.io\nDocumentation: Update references to deprecated world.emit() function | Description: Ensure documentation reflects the change to app.emit() | Mentioned By: Ashxn", "messageCount": 30, "userCount": 10 }, { "channelId": "958209074045026327", "channelName": "⚡│general", "summary": "# Discord Chat Analysis for \"⚡│general\"\n\n## 1. Summary\nThis chat segment contains minimal technical discussion. The conversation primarily revolves around a community call announcement, social media coordination for promoting the call, and brief interactions between community members. Maximus shared information about an upcoming community call and posted about it on Twitter, with CheddarQueso offering feedback on social media strategy. There was also a brief exchange about avoiding a potential scam attempt. The chat lacks substantial technical content, problem-solving discussions, or implementation details during this period.\n\n## 2. FAQ\nQ: Was the community call announcement tweet posted from the right account? (asked by CheddarQueso 🧀) A: Maximus posted it from his personal account, but Hyperfy retweeted it (answered by maximus)\n\n## 3. Help Interactions\nHelper: maximus | Helpee: ᲼~/^b0gie-(.*)$/ | Context: User appeared to encounter a potential scam and reacted instead of messaging | Resolution: maximus advised to tag him or general channel for faster response to security concerns\n\n## 4. Action Items\nType: Documentation | Description: Ensure community call announcements include dates | Mentioned By: maximus\nType: Feature | Description: Consider using official Hyperfy Twitter account for community announcements | Mentioned By: CheddarQueso 🧀", "messageCount": 25, "userCount": 10 }, { "channelId": "1326789867312775290", "channelName": "🪙│hyper", "summary": "# Analysis of Discord Chat in \"🪙│hyper\" Channel\n\n## 1. Summary\nThis chat segment contains minimal technical discussion. The conversation primarily consists of brief comments about token purchases, price movements, and exchange listings. Users mention buying more HYPER tokens amid price fluctuations. There's a mention of AI16Z being listed on Crypto.com, with speculation that HYPER might follow. Some users express concern about price drops, while others indicate they're buying during the dip. No substantive technical discussions, problem-solving, or implementations are present in this chat segment.\n\n## 2. FAQ\nQ: When will Hyperfy be listed on major CEX? (asked by simk) A: Unanswered\n\n## 3. Help Interactions\nHelper: maximus | Helpee: jar0d | Context: Unspecified issue that jar0d mentioned | Resolution: maximus claimed to have \"fixed it for him\" but no specific details were provided\n\n## 4. Action Items\nFeature: Consider more focus on token price as suggested by community | Description: Some users expressed interest in more discussion about token price performance | Mentioned By: cloudAI", "messageCount": 19, "userCount": 12 }, { "channelId": "1031058655581323324", "channelName": "🧊│3d-design", "summary": "# Discord Chat Analysis for 🧊│3d-design\n\n## 1. Summary:\nThe chat primarily focused on Hyperfy platform discussions, particularly around the transition from v1 to v2. A user (carlosmu) inquired about creating a new world in Hyperfy v1, leading to information from Ashxn about v1 being in maintenance mode with no major updates planned. Ashxn clarified that v2 is the current focus, with the world engine being open source and available for self-hosting or through services like hyperworld.host. Users can build locally or in play.hyperfy.xyz where everyone has build permissions. The documentation has moved from hyperfy.how to docs.hyperfy.xyz. Another user (untitled, xyz) asked about v1-friendly grass assets and was directed to a more appropriate channel for that question.\n\n## 2. FAQ:\nQ: I want to create a new world/land in Hyperfy v1. Is it not possible anymore? (asked by carlosmu) A: The v1 world nfts are no longer available and we're transitioning to a new v2 engine and platform. (answered by Ashxn)\nQ: Can I bought a world in opensea? (asked by carlosmu) A: Yeah you could but the v1 platform is in maintenance mode, no more major updates. It still works though. (answered by Ashxn)\nQ: Is there any chance to try the v2 builder or is it not released yet? (asked by carlosmu) A: Yeah the v2 world engine is open source, you can self-host it if you're savvy or use a hosting service like hyperworld.host. (answered by Ashxn)\nQ: Can we build locally? (asked by carlosmu) A: Absolutely. (answered by Ashxn)\nQ: Is this the right link for v2 docs? (asked by carlosmu) A: That moved to https://docs.hyperfy.xyz. (answered by Ashxn)\nQ: Is this v1 or v2 infrastructure? (asked by carlosmu) A: v2. (answered by Ashxn)\nQ: Is there a roadmap for the release of v2? (asked by carlosmu) A: Roadmap coming soon! (answered by Ashxn)\nQ: Anyone got some sweet v1-friendly grass I could use? (asked by untitled, xyz) A: Unanswered\n\n## 3. Help Interactions:\nHelper: Agent12 | Helpee: untitled, xyz | Context: User needed v1-friendly grass assets | Resolution: Suggested asking in a more appropriate channel (#1012527849024004167)\nHelper: Ashxn | Helpee: carlosmu | Context: User wanted to create a new world in Hyperfy v1 | Resolution: Explained v1 limitations and provided v2 alternatives including self-hosting, hyperworld.host, and building in play.hyperfy.xyz\n\n## 4. Action Items:\nDocumentation: Check updated v2 documentation at docs.hyperfy.xyz | Mentioned By: Ashxn\nTechnical: Try building in play.hyperfy.xyz where everyone has build permissions | Mentioned By: Ashxn\nTechnical: Consider self-hosting v2 world engine or using hyperworld.host | Mentioned By: Ashxn\nFeature: Wait for upcoming v2 roadmap | Mentioned By: Ashxn", "messageCount": 26, "userCount": 6 }, { "channelId": "1330373197203505185", "channelName": "🤖│agents", "summary": "The chat segment is extremely brief, consisting of only two messages. Maximus shared a link to a Coinbase Developer Platform page about \"x402\" with an expression of surprise (\"Holy moly\"). Ashxn responded with a one-word acknowledgment (\"crazy\"). There is no substantive technical discussion, problem-solving, or implementation details in this exchange.", "messageCount": 2, "userCount": 2 }, { "channelId": "1347905902937767997", "channelName": "🔉│community-updates", "summary": "# Analysis of 🔉│community-updates Channel\n\n## 1. Summary\nThis Discord message from maximus announces an upcoming Community Call with several key topics. The message highlights recent technical developments and community contributions in the Hyperfy platform. Major announcements include a planned UI overhaul based on user feedback, updates to the Hyperfy Platform experience, and possible vehicle implementation. The message showcases various community projects including Gert-Jan's NEON sign app (now in v2), Vox's lightweight world magic, improvements to scaling and level of detail (LOD), b0gie's door mechanics, cru's power admin UX prototype, Peezy's hypkg UI integration, and agent functionality in Hyperfy worlds. The message also references external content relevant to Hyperfy's development direction, including a conversation between Tim Sweeney and Lex Fridman. The community call is scheduled to address these developments and respond to community questions, including when vehicles will be implemented.\n\n## 2. FAQ\nQ: Wen vehicles? (asked by Community) A: Unanswered (but listed as a topic for the upcoming Community Call)\n\n## 3. Help Interactions\nHelper: b0gie | Helpee: Parzival89 | Context: Door mechanics implementation | Resolution: Shared door magic work as referenced in Twitter post\nHelper: Gert-Jan | Helpee: Community | Context: NEON sign app development | Resolution: Released version 2 of the NEON app\n\n## 4. Action Items\nType: Technical | Description: Major UI overhaul based on feedback and prototypes | Mentioned By: maximus\nType: Technical | Description: Hyperfy Platform experience update | Mentioned By: maximus\nType: Feature | Description: Vehicle implementation in Hyperfy | Mentioned By: maximus\nType: Technical | Description: Improvements to scaling and level of detail (LOD) | Mentioned By: maximus\nType: Technical | Description: Integration of hypkg into the UI | Mentioned By: maximus\nType: Technical | Description: Agent functionality in Hyperfy worlds | Mentioned By: maximus", "messageCount": 1, "userCount": 1 }, { "channelId": "999870741069692958", "channelName": "🌆│share", "summary": "No technical discussions, decisions, or problem-solving occurred in this chat segment. The only message was from user Rick sharing a tweet about a \"WIP Meetup\" that had taken place, with a reference to pictures shared under a video.", "messageCount": 1, "userCount": 1 } ] }