Was this change done because there was perhaps an optimization added to FindFirstChild :)?
Perhaps it’s now fast enough to be relied on in tight loops :)?
Please I kindly ask you revert this change or allow us to hide the error as it is causing us major inconveniences.
2 Likes
Many built in features and plugins are now unusable. For example, I can no longer update or view the vast majority of my plugins in the Manage Plugins window. I genuinely see no reason for this change. The documentation should be made to reflect the engine, not the other way around.
2 Likes
What a great update. Spend time and resources REMOVING functionality that will break thousands of games and hasn’t been an issue for the last 18 years of this platform’s existence while hundreds of other features are broken. Awesome!
3 Likes
Based on feedback, the warning has been disabled.
14 Likes
It’s a warning that doesn’t affect old behavior, it doesn’t have to be fixed immediately.
Having a note wouldn’t helped here because developers are often not even aware when engine APIs are being incorrectly used. Warning message (not an error) was designed to show places with potential mistakes.
The engine will still convert number, table (to table: 0xpointer), Part (to Instance) etc… to preserve existing behavior, but warning will show potential issues.
They don’t, now that it’s actually possible to see the issues, Roblox teams are working on fixing CoreScript issues (and finding hidden bugs).
Behavior of the functions didn’t change, all games will continue working as they did before.
Warning message is the grace period, without a message developers will not be aware of any issues.
This change was based on a feature request from the developer community.
Warning message is the notice.
The change is backwards compatible and doesn’t change the behavior of the engine.
According to bug reports we receive, this was one of the broken features we fixed here.
11 Likes
What request? This feels like a slip up, and it’s worrying that things like this can just happen. I don’t see any reason why this change needed to be made, and all you’ve responded with is “the behavior didn’t change” and “these warnings are the grace period”. No announcement, no nothing, just a sudden 180 in normal functionality passed off as a “feature request”. Not a good look. I can’t help but wonder if I’m missing something here.
3 Likes
To be clear, I am in support of this warning message. I can definitely see tons of bugs being revealed through this warning.
Well it is helpful to me because it immediately tells me if the new warnings are from a Roblox change or a change we made. This is especially important when working with a team.
For example, a team member may have inadvertently made a change in our code base that brought these warnings on. In this case, we don’t know if the team member simply made a type error or if they also made a logic error that needs to be fixed.
I immediately checked the release notes after seeing these warnings. Had I not found this post I may have wasted extra time investigating the root cause of the warnings’ sudden appearance, assuming it was on our end.
2 Likes
My game hasnt been working since you’ve added this please fix it.
This warning has been removed.
If your experience is still failing, please open a new bug report with details to track the issue separately.
Don’t get the hostility. I don’t see how this is “bad”. This change’s only effect was to add random warnings out of nowhere
1 Like
I never knew this was actual behavior and it isn’t documented. If you complain about these warnings it’s simply due to your ignorance; because FFC strictly states it takes a string
1 Like
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.