Cyantrigger broken with latest SDK release
closed
Lakuza
A few creators have reported that Cyantrigger does not work anymore on the latest beta sdk, I don't have any logs myself since I don't want to risk updating any of my own projects so I'll just quote what the creators have said (assuming they didn't make any canny posts on this):
Enverex:
"Failed to compile due to error: Ambiguous match found." another error about someone being null, despite no entries being null.
Miner:
"Yes, the networked params completely broke it, it's due to it not being able find correct method"
Hope these are helpful in some way, since a lot of creators rely on cyantrigger to make their worlds (me included).
Log In
kawashirov
I wanted to write my thought here, but as it is closed now, I dropd it into twitter
Μerlin
Going to note that going by the error message, this appears to be something VRChat could fix by just changing the name of the SendCustomNetworkEvent functions that take parameters. In other words, VRChat can technically fix this and their stance of "we can't fix this" seems to be in reality "we don't want to fix this." This would of course be a breaking change so VRC should've done this during beta if they cared to fix the issue. It's preferable IMO if they can come to an agreement with Cyan to either fix it in CyanTrigger themselves or have Cyan fix it especially considering they chose to back themselves into a corner. Failing that VRChat can keep existing worlds working if they define Udon externs that only exist in-client with the old signature and change the method name to avoid ambiguity in new SDKs.
Sayamame
Μerlin
Certainly, technically, it would be fixed by renaming the
SendCustomNetworkEvent
that takes parameters or the SendCustomNetworkEvent
itself, but I don't feel that is reasonable.I think that adding another method such as
SendCustomNetworkEventWithParam
or renaming the entire method to something like SendCustomNetworkingEvent
would not only cause a compatibility issue but also be really confusing for users.Μerlin
Sayamame Pasting response I gave in discord
They could shorten the method to SendNetworkEvent and it'd likely be better than what they have for usability, could also add a non-parameter overload for consistency.
Compatibility issues were avoidable but VRChat chose to ship the API as-is.
Sayamame
Μerlin
I understand that shortening it to
SendNetworkEvent
might improve usability, but I still think renaming itself would be confusing.Μerlin
Sayamame Sure, it'd be preferable if they could figure out something with Cyan. But between the name change being potentially confusing to a few people, and killing trigger scripting again I think there are valid tradeoffs to make. It's also possible to mark the existing SendCustomNetworkEvent as
[Deprecated("SendCustomNetworkEvent is deprecated, use SendNetworkEvent instead")]
that'd keep SendCustomNetworkEvent that people are more familiar with working while pointing people towards the updated version.GenesisAria
Μerlin VRChat? actually use versioning? and sandboxing depreciated legacy methods? Blasphemy! Progress must march on! Down with those "stuck in the past"... Not like we need accessibility anyway.
Strasz - Community Team
closed
Angriffsmacht
Strasz - Community Team
Pretty bold to break something, leave a mess behind, and then just act like nothing happened and try to move on.
Have you even looked at how many worlds you’re about to destroy with this?
CyanLaser made it clear on Bluesky that you didn’t even try to reach out.
We can all see that you never even opened a ticket on his Github.
All you’re doing is causing damage and now you’re just pointing fingers at others!
｜KitKat｜
Strasz - Community Team
Very disappointing decisions being made here.
Strasz - Community Team
Unfortunately, this update will break CyanTrigger. This shouldn't impact existing content, but moving forward, CyanTrigger won't work with this version of the SDK (or, likely, future versions of the SDK). This isn't something that is currently fixable on our end.
PK
Strasz - Community Team yikes, that means basically that after a decade, whenever the sdk's advance enough that i have to update, i might be cut out of worldbuilding unfortunately. unless someone creates a way to do it without having to learn coding language.
BluWizard
Strasz - Community Team This is absolutely the most selfish decision you have made. You have basically just given the biggest middle finger to almost every single goddamn Creator out there who has relied on this system to build their Worlds, Lakuza included. Bullet Time Agent was made with lots of CyanTriggers, and now you just want to throw that all away??!!
Do better, VRChat. This is an absolutely SHAMEFUL decision! You could of at least lessened the burden by making it less harder for people to use Udon, like making your own version of CyanTrigger. For gods sake, can we please go ONE DAY without a breaking decision by the VRChat Devs??!! Jesus…
The Snooze
Strasz - Community Team I feel like it iss fixable on your end but its like the internal team think its not worth the effort. CyanTrigger has been used by hundreds of creators over the years some have used it as a stepping stone to coding like I have and some sticks by it because that's where they perform the best.
It's kinda cold to to just stop supporting something that has meant so much to so many people just like that.
You guys should reconsider this. This is just so wrong and its not the first time odd decisions are being made.
Strasz - Community Team
The Snooze: This is not fixable on our end. CyanTrigger is no longer maintained by them. We could potentially fix this, but CyanTrigger's license does not permit updates/fixes from anyone but Cyan.
Angriffsmacht
Strasz - Community Team
There’s something people can do—it’s called talking.
Hey, that’s even THE main feature of VRC.
So why couldn’t you, as staff, manage to actually talk to CyanLaser?
｜KitKat｜
Strasz - Community Team
"This is not fixable on our end."
What about the suggested solutions posted in this thread?
Raifa
Strasz - Community Team look, i know it isn't only your fault, and i understand the frustration of everyone pinging you on this issue.
But it looks like there's conflicting facts being spoken here. Can you clarify if Merlin's post is valid? That
is
a fixable issue on your side. If it isn't, would you mind sharing with us why that is, and why this breaking change was necessary? Unless that's done, the community's going to continue looking at this as a bad and lazy decision made by the team.
PK
yikes! found this when trying to source the issue around people saying one of my worlds was broken. if cyantriggers bugs out that means everything i've made over many years is unreliable, and i'd have to completely relearn new systems in order to make anything new. cyantriggers took long enough to learn the basics, working with udon directly feels beyond me.
Sekathi
PK Creates the most incredible, multi-hour VR experiences available in VR. The sheer amount of value of his ART that would be lost if they were to break is indescribable. It literally would be a tremendous loss to 3D Art & Audio/Visual community and digital history. Videos don't do it justice, some of the effects are impossible to experience the full effect without a VR headset.
StormRel
tracked
Salena
Leaving this here as I rely on this heavily, this occurs in a new project with just CyanTrigger 4.4.3 and a blank CyanTrigger component. SDK beta [3.8.1-beta.3]