May 22nd 2025: A large number of spam user accounts have been removed from the wiki. If your account was accidentally deleted during this process, please get in contact to have it restored!

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
guide:communication [2025/11/05 16:35] – [OnCommunicate] Update listing of how each SHIORI handles communication, to make it less dense and fix the problem of curly quotes ulde3guide:communication [2025/11/05 16:45] (current) – [Sending and receiving external SHIORI Events] Fix broken syntax ulde3
Line 58: Line 58:
  
 === Target === === Target ===
-raiseother and notifyother tags can either send their events to specific targets, or they may use ''__SYSTEM_ALL_GHOST__'' to target every open ghost at once. Which is ideal for your event depends on what you are making.+raiseother and notifyother tags can either send their events to specific targets, or they may use ''<nowiki>__SYSTEM_ALL_GHOST__</nowiki>'' to target every open ghost at once. Which is ideal for your event depends on what you are making.
  
-For example, if your ghost has a music player function and you want other ghosts to be able to tell what song is playing, it's probably best to send that information to every open ghost at once with ''__SYSTEM_ALL_GHOST__''. That way any ghost can simply receive the info and handle it as they see fit with no additional steps.+For example, if your ghost has a music player function and you want other ghosts to be able to tell what song is playing, it's probably best to send that information to every open ghost at once with ''<nowiki>__SYSTEM_ALL_GHOST__</nowiki>''. That way any ghost can simply receive the info and handle it as they see fit with no additional steps.
  
 On the other hand, for a function like [[ghost:Needle]]'s ghost poking, where Needle sends the event OnNeedlePoke after overlapping with a ghost, it makes sense to only send the event to the ghost that was specifically poked. On the other hand, for a function like [[ghost:Needle]]'s ghost poking, where Needle sends the event OnNeedlePoke after overlapping with a ghost, it makes sense to only send the event to the ghost that was specifically poked.

Trace:

Explore Content

Ghosts

Balloons

Freeshells

Calendar Skins

Plugins

SAORI

Tools

Guides

Templates

Events