Scripting Helpers is winding down operations and is now read-only. More info→
Log in to vote
0
What actually happens when you reference an ObjectValue's value?
I am getting the error: Workspace.SteamG0D.ControlScript:14: attempt to index upvalue 'V' (a nil value)
What I am trying to do is have a script give assign it's parent to the value of an ObjectValue, which does work, and then once that happens, another script (a local script inside the player character) applies actions to the parts inside the ObjectValue's referenced object.
01 | local uis = game:GetService("UserInputService") |
02 | local player = script.Parent |
03 | local V = player.Obj.Value --player.Obj is the ObjectValue |
04 | local light = false |
05 |
06 | uis.InputBegan:Connect(function(Input, IsTyping) |
07 | if Input.KeyCode == Enum.KeyCode.Y and not IsTyping then |
08 | if light then |
09 | print("Y has been pressed OFF") |
10 | V.Base.BodyForce.Force.Y=0 |
11 | else |
12 | print("Y has been pressed ON") |
13 | V.Base.BodyForce.Force.Y=workspace.Gravity |
14 | end |
15 | end |
16 | end) |
0
You're setting V to the VALUE of your ObjectValue, not setting it as a pointer to whatever the value happens to be at the current time. If you set it at the start and it's nil, it will be nil forever. fredfishy 833 — 6y
0
@fredfishy is there any way to set an object as a pointer to a value then? SteamG00B 1633 — 6y
1
You can't, and you don't need to. I can write up an answer if you want, so I can explain the difference between a pointer and a value. If you're meaning a pointer to the property . User#24403 69 — 6y
0
I understand the difference, I just wasn't sure if ObjectValues acted as a pointer or not, hadn't ever used them before. Now the reason why I do need to store a pointer to an object is so that I can have a player script apply actions to parts in an object that won't be known until my player sits in a seat. SteamG00B 1633 — 6y
View all comments (6 more)
0
Just make a direct access to the Value property of the ObjectValue. User#24403 69 — 6y
0
I don't understand what you mean by that, I thought that's what i was doing. SteamG00B 1633 — 6y
0
It seems you got confused there, I'm trying to store a pointer to an object, not a pointer to a value, a pointer to a value wouldn't make sense. SteamG00B 1633 — 6y
0
I mean, plr.Obj.Value User#24403 69 — 6y
0
Whenever you need to change the value or just need to fetch it, make a direct access User#24403 69 — 6y
0
well the problem with that is that it returns a nil value eventhough it has clearly been set to something, I can set it to something (I literally hunted it down in the workspace and it appeared to have the correct value set to it), but it still gives an error message saying it is a nil value SteamG00B 1633 — 6y