Release Notes for 377

[LuaCow]

Notes for Release 377

[Maximum_ADHD]

Client Difference Log

0.377.1.289039

API Changes

Added Class AngularVelocity : Constraint
	Added Property Vector3 AngularVelocity.AngularVelocity
	Added Property float AngularVelocity.MaxTorque
	Added Property Enum<ActuatorRelativeTo> AngularVelocity.RelativeTo
	
Added Function void AnalyticsService:TrackEventWithArgs(string category, string action, string label, Dictionary args, int64 value = 0) {RobloxScriptSecurity}
Added Function Instance Players:CreateHumanoidModelFromDescription(Instance description, Enum<HumanoidRigType> rigType) {RobloxScriptSecurity} [Yields]
Added Function Instance Players:CreateHumanoidModelFromUserId(int64 userId) {RobloxScriptSecurity} [Yields]
Added Function Enum<DeviceType> UserInputService:GetDeviceType() {RobloxScriptSecurity}

Added Enum DeviceType
	Added EnumItem DeviceType.Unknown : 0
	Added EnumItem DeviceType.Desktop : 1
	Added EnumItem DeviceType.Tablet : 2
	Added EnumItem DeviceType.Phone : 3

Added Tag [Hidden] to Property StarterPlayer.CharacterJumpHeight
Added Tag [Hidden] to Property StarterPlayer.CharacterJumpPower
Added Tag [Hidden] to Property StarterPlayer.CharacterMaxSlopeAngle
Added Tag [Hidden] to Property StarterPlayer.CharacterUseJumpPower
Added Tag [Hidden] to Property StarterPlayer.CharacterWalkSpeed

Changed the category of Property Humanoid.AutoJumpEnabled
	from: "Control"
	  to: "Jump Settings"
	  
Changed the category of Property Humanoid.JumpHeight
	from: "Game"
	  to: "Jump Settings"

Changed the category of Property Humanoid.JumpPower
	from: "Game"
	  to: "Jump Settings"

Changed the category of Property Humanoid.UseJumpPower
	from: "Game"
	  to: "Jump Settings"

Changed the parameters of Function Plugin:ImportFbxAnimation 
	from: (Instance rigModel)
	  to: (Instance rigModel, bool isR15 = true)

Changed the parameters of Function Plugin:ImportFbxRig 
	from: ()
	  to: (bool isR15 = true)

Changed the security of Property StarterPlayer.CharacterJumpHeight 
	from: {None}
	  to: {RobloxScriptSecurity}

Changed the security of Property StarterPlayer.CharacterJumpPower 
	from: {None}
	  to: {RobloxScriptSecurity}

Changed the security of Property StarterPlayer.CharacterMaxSlopeAngle 
	from: {None}
	  to: {RobloxScriptSecurity}

Changed the security of Property StarterPlayer.CharacterUseJumpPower 
	from: {None}
	  to: {RobloxScriptSecurity}

Changed the security of Property StarterPlayer.CharacterWalkSpeed 
	from: {None}
	  to: {RobloxScriptSecurity}

(Click here for a syntax highlighted version!)

[Dekkonot]

When will the horrors end?

[Extuls]

Clearly 2019 cannot bring a better update than this. So happy to see that terrible behavior go.

[devSparkle]

Ah. Ahh. Aaaaahh. So this is why I kept closing studio ever so often for the past 10 years…

[Noble_Draconian]

The URL for the release notes is invalid.

[Maximum_ADHD]

It may have been down temporarily due to a publishing issue. Seems to be working fine now.

[Noble_Draconian]

Still down for me. I can’t access any of the past release notes.

[Maximum_ADHD]

Try doing a hard-refresh with Shift + F5.

[T0ny (Tophat)]

Did an empty cache hard refresh, but it’s down for me as well.

[Operatik]

Can confirm that I cleared out the cache in attempts to access the page did not work. It’s still down regardless. I’ll wait until tomorrow and check if the page is accessible.

[iiau]

Added Enum DeviceType
	Added EnumItem DeviceType.Unknown : 0
	Added EnumItem DeviceType.Desktop : 1
	Added EnumItem DeviceType.Tablet : 2
	Added EnumItem DeviceType.Phone : 3

We’ll soon finally have a way to know which device the player is on accurately. This is wonderful.

Edit: Probably not.

[buildthomas]

Not quite, read the list carefully. The only place where DeviceType is used is here:

Added Function Enum<DeviceType> UserInputService:GetDeviceType() {RobloxScriptSecurity}

Note the “RobloxScriptSecurity”. This method will not be usable for developers.

[iiau]

That kinda defeats the purpose, then

We need a better way to detect devices. I’m skeptical why this isn’t unlocked.

[buildthomas]

Read the whole discussion here on why you probably do not need to know what device a player is playing on:

Device Type Detection

I’ve made a similar request in the past, but I’m coming back with a more refined request. Sometimes it can be very useful to tell what type of device a user is on (such as console, PC, mobile…). However, there is currently no way to explicitly check and see what device the user is on. And so game devs are forced to do hacky tricks to figure out what device the user might be on. I emphasize “might” because it is not a guarantee and there are holes in the logic. My proposal: Player.DeviceType …

Knowing the device is only really useful for analytics. You don’t actually want to base anything else off of device type, just use input mode.

[devSparkle]

It’s also useful if I wish to create custom servers only for a particular set of devices. Overall, it’s a reasonable request.