Server [Rockford/Build/Event]: All im assuming, but only tested on rockford
Map (if not default):
Description: Right clicking any player on the AFK team gives a lua error
Bug observed since: Now
Images/Screenshots:
[ERROR] gamemodes/cityrp_2_by_limelightgaming/gamemode/core/scoreboard/player_row.lua:68: attempt to concatenate a nil value
1. DoRightClick - gamemodes/cityrp_2_by_limelightgaming/gamemode/core/scoreboard/player_row.lua:68
2. unknown - lua/vgui/dlabel.lua:227
Thank you for your bug-report, Tails!
It will be reviewed as soon as possible by our Developers.
This isn't the case for me. Can anyone else reproduce this?
(Oct 9, 2017, 04:49 PM)Nightmare Wrote: [ -> ]This isn't the case for me. Can anyone else reproduce this?
Doesn't happen for me either.
Would this be due to there being nothing in the job name
As nil means nothing, or no value not even 0.
Does this happen when [AFK] is present?
(Oct 10, 2017, 07:41 PM)Stell90 Wrote: [ -> ]Would this be due to there being nothing in the job name
As nil means nothing, or no value not even 0.
Does this happen when [AFK] is present?
Happens when their job is blank, shown just as "[]"
(Oct 10, 2017, 08:03 PM)Tails Wrote: [ -> ] (Oct 10, 2017, 07:41 PM)Stell90 Wrote: [ -> ]Would this be due to there being nothing in the job name
As nil means nothing, or no value not even 0.
Does this happen when [AFK] is present?
Happens when their job is blank, shown just as "[]"
Well that would explain why then. Im not 100% sure as I had it in the past but I dont remember.
If you pressed tab again doesn't it fix its self? Or does it just stay the same.
If it fixes its self I would say its client side but dont quote me.
(Oct 10, 2017, 08:07 PM)Stell90 Wrote: [ -> ] (Oct 10, 2017, 08:03 PM)Tails Wrote: [ -> ] (Oct 10, 2017, 07:41 PM)Stell90 Wrote: [ -> ]Would this be due to there being nothing in the job name
As nil means nothing, or no value not even 0.
Does this happen when [AFK] is present?
Happens when their job is blank, shown just as "[]"
Well that would explain why then. Im not 100% sure as I had it in the past but I dont remember.
If you pressed tab again doesn't it fix its self? Or does it just stay the same.
If it fixes its self I would say its client side but dont quote me.
nah, even rejoined a couple times and that didn't seem to fix it either
Got this problem aswell, i think (maybe) I made a bugreport a long time ago on This
I'm sure this is fixed now.
I have seen it for a long time now.
Should have been fixed by the ndtworking changes.
![[+]](/forums/images/collapse_collapsed.png "[+]")
Spoiler