Skip to content

Conversation

@axxroytovu
Copy link
Contributor

No description provided.

Adds event visibility to the slot data
Checks the slot data to read which events should be visible
Adds events that are visible to the item list with appropriate categories
@axxroytovu
Copy link
Contributor Author

axxroytovu commented Mar 28, 2025

Ok, we're very close. Events now have an optional "visible" tag that will make all copies of that event visible in the client. Still to-do:

  • More rigorous testing
  • Add syntax example for visible
  • Add schema

@axxroytovu axxroytovu marked this pull request as ready for review March 28, 2025 22:01
nicopop
nicopop previously approved these changes Mar 29, 2025
Copy link
Contributor

@nicopop nicopop left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Im approving without testing it since silasary said they would test, that and the code look good

@FuzzyGamesOn FuzzyGamesOn added the paused for client updates Until further notice, only bugfixes will get merged for the client label Apr 17, 2025
@silasary silasary mentioned this pull request Apr 20, 2025
@FuzzyGamesOn FuzzyGamesOn removed the paused for client updates Until further notice, only bugfixes will get merged for the client label Sep 10, 2025
@FuzzyGamesOn
Copy link
Collaborator

Removed the client paused label from this PR. At a glance, looks like a great addition. Will circle back to review.

Ideally, we'd have some user-facing documentation to explain the new events feature, as this is likely to get a lot of use. I feel like you had documentation already for doing events in a Manual apworld, so might be able to repurpose some of that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants