-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Lua Error #98
Comments
What were you doing when you received the error?
…On Sun, May 14, 2017 at 07:40 Aka7tsu4 ***@***.***> wrote:
Steps to reproduce
1.
2.
3.
Expected behavior
Tell us what should happen
Actual behavior
Tell us what happens instead
Error(s) in server console, if any
[[Prisel] Mugiwara Zoro|1174|STEAM_0:0:201161789] Lua Error:
[ERROR] addons/ulib/lua/ulib/shared/player.lua:121: Tried to use a
NULentity!
1. indexFn - [C]:-1
2. getUniqueIDForPlayer - addons/ulib/lua/ulib/shared/player.lua:121
3. runCmd - addons/ulx/lua/ulx/xgui/commands.lua:266
4. DoClick - addons/ulx/lua/ulx/xgui/commands.lua:236
5. unknown - lua/vgui/dlabel.lua:232
Error(s) in player's console, if any Version
Run "ulx version" in console and paste the result
14:39:30 - ULib v2.63
14:39:30 - ULX v3.71d
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#98>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABAz13PMKbgcDHIMVb0KYowCxUXLTIfks5r5vZSgaJpZM4NaXbd>
.
|
No response from OP for quite some time, closing issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Steps to reproduce
Expected behavior
Tell us what should happen
Actual behavior
Tell us what happens instead
Error(s) in server console, if any
[[Prisel] Mugiwara Zoro|1174|STEAM_0:0:201161789] Lua Error:
[ERROR] addons/ulib/lua/ulib/shared/player.lua:121: Tried to use a NULentity!
Error(s) in player's console, if any
Version
Run "ulx version" in console and paste the result
14:39:30 - ULib v2.63
14:39:30 - ULX v3.71d
The text was updated successfully, but these errors were encountered: