The MouseBehavior API is far superior as it’s easier to add new functionality.
2 Likes
MouseBehaviour API doesn’t change shiftlock state
that’s why you add those as a feature?
1 Like
What I originally meant is, MouseLock and MouseBehavior are entirely different.
You can test this by working with MouseBehaviour, if you set it to locked it doesn’t change the image. This doesn’t mean it’s terrible or anything, I support this as MouseLock has always been weird (considering DevEnableMouseLock was only server-sided, even though it could still be exploitable, and there was no good way around to setting MouseLock state without modifying the PlayerModule).
Ever since MouseBehavior has been added, everything has been made better. My point was that MouseBehavior and MouseLock have nothing to do, and you can see this by checking the camera modules, you’ll notice it (both behave exactly the same but MouseBehavior is far superior because it can be customized, unlike the preset MouseLock image, for example).
TL;DR: If you add a local script that sets MouseBehavior to a locked state, and go to the roblox menu, as an example, you could have shiftlock off and mousebehavior locked:
you can see both do not have anything to do between them in these pictures, because even with shiftlock off its still locked, which is good, because developers should disable DevEnableMouseLock and add their own functionality
ignore the output
FYI–I’ve seen some people nervous about the deprecation of the CollectionService methods here and interpreting it as a deprecation of tags as a system entirely. This is definitely not the case! The new methods are just more convenient ways of accessing their respective methods (Instance:GetTags() is CollectionService:GetTags(instance)).
7 Likes
This QoL update was one I’ve been wanting for the longest!
Does this mean CollectionService:GetTagged will be deprecated as well?
@DataSigh Yes, that looks correct.
@2jammers No, as that wouldn’t be sane as a method on instance. :HasTag, :RemoveTag, :AddTag, and :GetTags are what are now on Instance and no longer need to be pinged through CollectionService.
2 Likes
Ok that makes sense, but would this break games if CollectionService is inherited from Instance? I like the new methods, but it looks like the new Instance methods would just override CollectionService methods.
Nope, we’ve had these enabled for a while and haven’t heard of any breakages. CollectionService’s implementation takes priority.
1 Like
This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.