
Recent changes to the Creator Portal have simplified how creators publish and manage their projects. While these updates are geared towards clarity and efficiency, some users voice concerns over unresolved issues with older islands.
The team has refined terminology to streamline the publishing process, aiming for ease of understanding:
Publish now only refers to approved island releases accessible to players.
Create a release involves submitting an island for review.
Active release is officially swapped for Published release.
Inactive release has become Unpublished release.
By making these adjustments, the team hopes to reduce confusion throughout the management stages.
A new visibility framework helps creators understand their islands' status:
Listed: Islands live and visible on public pages.
Unlisted: Playable but hidden; only accessible via code.
Unpublished: Not publicly available, affecting engagement metrics.
Curiously, users can't deactivate an island; they must now choose to unpublish it instead, creating a streamlined category for all non-public projects.
Another update includes filtering options on the Projects page, allowing creators to track performance more effectively. According to feedback, some users feel the enhancements fail to cover older disabled islands. One noted, "Thereโs no actionable data for islands disabled years ago."
Feedback varies, with several users expressing mixed feelings:
Many appreciate the clearer language, seeing it as a positive step forward.
Others argue the improvements don't fully address their needs, especially concerning legacy islands.
As one participant remarked, "Player support does not have access to these islands to help in any way."
A representative from the team invited users to share their concerns on forums, stating that the team is aware and may respond soon.
๐น Streamlined Terms: Enhanced terminology benefits project management.
๐ธ New Filtering System: Allows for better performance tracking.
โ ๏ธ Legacy Concerns: Outstanding issues related to older islands persist.
As updates roll out, the development team plans to prioritize community feedback. Experts suggest about 70% of users could see better access to support systems in the future. While clear communication seems to pave the way for smoother interactions, unresolved legacy issues remain a sticking point for many, potentially pushing some users to seek alternatives with more comprehensive management features.
Historical trends indicate that addressing community concerns is essential for maintaining engagement, similar to past shifts in online platforms. If the team fails to resolve ongoing issues, the dissatisfaction expressed by a portion of the community may impact future participation.