My friend wants to implement VR support into his game with the Nexus VR System, but he says that he doesn’t want to make the game R15 to everyone (The VR System requires R15). He says that for now he just wants only certain people to be able to use it and have some sort of whitelist. I have tried looking for a solution but can’t find one anywhere. How can I go about forcing a player into R15 if they are on a whitelist when the game forces R6?
Edit: Attempting to change the RigType on the humanoid just kills the player.
I’m confused. The game is R15 compatible. Why would someone want to force some people to using the old characters if the game works with R15? Why go through so much trouble to give the characters only to select players?
Ultimately don’t think it is possible. I’ve tried a few options in the past.
Eg. Setting the RigType to R15 right as the character is added. (Yeah it didn’t work, results might be funny though)
A character’s RigType likely is set by the Roblox’s internal C++ scripts. As you can change your characters RigType in the avatar editor and reset your character in-game and it’ll spawn with that Rig. And because you cannot edit the internal scripts there probably is zero way to do this.
If someone could figure out how I’d be amazed. It’d probably be really hacky though.
Not true. There are R6>R15 converters in the toolbox even. It is fairly hacky as you mentioned however. I remember people constantly complaining about the dead state triggering. Regardless, it is possible.
1.Make an R15 StarterCharacter
2.Check if player joined is your friend
3.Delete parts inside the current character’s group
4.Clone parts inside R15 StarterCharacter into the current character’s group
5.Change CameraSubject to the new humanoid.
But if you’re a lazy pig like me, here’s my code.
local player = "use your own method to find out player, this was originally a remote event"
print(player.Name, "has selected ASSAULT loadout")
--Delete parts inside player's character but not the group
local oldchar = player.Character:ClearAllChildren()
wait()
--Clone Custom Character and parent it to player's character
local a = game.ServerStorage.Assault:Clone()
a.Parent = player.Character
local p = a:GetChildren()
--Unparent the new parts because they are in a different group
for i = 1,#p do
p[i].Parent = player.Character
end
--Reset camera so you can control character
workspace.Camera.CameraSubject = player.Character
~hacky codes~
Hope this helps kbye
(how i make my custom morphs for my games lol)
Setting a StarterCharacter means you’re forcing a certain look or avatar make upon everyone. There isn’t a real way to do “select StarterCharacters” because then it isn’t a StarterCharacter anymore.
Stages 3-5 don’t work because the death state will get triggered unless you disable it off on the server and client first. That and you get whack results if you put a R15 setup without setting the RigType.
@OP
In the first place, I don’t think it’s really good for your game to have two avatar types. Pick one or the other. You already have R15 compatibility for some components so why stop there? Make everyone use R15. I find for my places that using both avatar types is horrible and stress inducing to make the game compatible with two avatar types. It’s easier to use only one.
@ZacBytes You miss my case in point and ignored the rest of what I said to reply to my first statement.
@grilme99 That… I’ll be honest, sounds like a poor game scheme. If you’re going to have R6 to main with because it’s a swordfighting game, why include any R15 at all? Sounds pretty useless imo to have VR and support R15 for a minority who won’t even use it often.
