Skip to content
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

Character Records dont show in game #3135

Closed
2 of 3 tasks
K4rlox opened this issue Apr 23, 2023 · 3 comments
Closed
2 of 3 tasks

Character Records dont show in game #3135

K4rlox opened this issue Apr 23, 2023 · 3 comments
Labels
Bug Admin events aren't bugs Duplicate It's already been done before

Comments

@K4rlox
Copy link

K4rlox commented Apr 23, 2023

Testmerges

#3073 #2984 #3118 #3129

Description of the bug

the security records and medical records that is entered into the character records in fluff information tab do not show in ingame character or medical records, due to this it cant effect character roleplay in certain situations

What's the difference with what should have happened?

the info entered into character records should have shown up in the person's records

How do we reproduce this bug?

  1. open character setup
  2. go to character records in fluff info
  3. enter anything into any of the records
  4. join a game
  5. go to a medical or security records console
  6. look up the person's records
  7. empty records

Issue Bingo

@K4rlox K4rlox added the Bug Admin events aren't bugs label Apr 23, 2023
@ItsVyzo
Copy link
Contributor

ItsVyzo commented Apr 23, 2023

#30

@ItsVyzo ItsVyzo closed this as not planned Won't fix, can't repro, duplicate, stale Apr 23, 2023
@ItsVyzo ItsVyzo added the Duplicate It's already been done before label Apr 23, 2023
@K4rlox
Copy link
Author

K4rlox commented Apr 25, 2023

@ItsVyzo
existing issue is from 2022 and its not fixed nor is anybody planning to fix it

also theres a 3000 issue gap between these if you can see.

@ItsVyzo
Copy link
Contributor

ItsVyzo commented Apr 25, 2023

@ItsVyzo existing issue is from 2022 and its not fixed nor is anybody planning to fix it

also theres a 3000 issue gap between these if you can see.

Duplicate is duplicate.
Having 1000 issues that report the same issue doesn't help.
If you can code and can fix it great, otherwise it's until someone who volunteers his time decides to do it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Admin events aren't bugs Duplicate It's already been done before
Projects
None yet
Development

No branches or pull requests

2 participants