HapticService:SetMotor has incorrect method signature

Bug Reports Documentation Issues
#1

Reproduction Steps
Look at the documentation for SetMotor:
HapticService:SetMotor (roblox.com)

It lists the third argument as a tuple of intensities. However, only one number is accepted.

How do I know? Well, adding anything after the third argument doesn’t do anything. I can literally write:

HapticService:SetMotor(Enum.UserInputType.Gamepad1, Enum.VibrationMotor.Small, 1, "abc", true, false, 32)

It doesn’t care about any arguments past the third.

Expected Behavior
The third argument should be a single number, and it should be listed as such in the API docs.

Actual Behavior
The third argument is listed as a tuple.

Issue Area: Studio
Issue Type: Other
Impact: Low
Frequency: Constantly

4 Likes
#2

This looks like a documentation issue rather than a Studio-specific issue, I’ll move this over to #bug-reports:documentation-issues for now.

2 Likes
#3

Hi there,
Apologies for the delay in responding to this. The last argument is a tuple to keep it open to future expandability, but as noted, only the first value is currently regarded. I’ve added a bit more emphasis for this in the docs, citing that it (the first value) should be a number.

Take care,
IgnisRBX

1 Like
#4

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.