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

Psionics Coercion Mind Reading Character Limited #205

Open
2 of 5 tasks
Menkhu opened this issue Nov 29, 2021 · 4 comments · Fixed by NebulaSS13/Nebula#2248
Open
2 of 5 tasks

Psionics Coercion Mind Reading Character Limited #205

Menkhu opened this issue Nov 29, 2021 · 4 comments · Fixed by NebulaSS13/Nebula#2248

Comments

@Menkhu
Copy link

Menkhu commented Nov 29, 2021

Description of issue

Replies to coercion mind reading questions seem to be severely limited by length. They also don't give any indicator to the mind reader or the person being read when the length is too long. The answers seems to be submitted by the person being read, and the mind reader receives the normal 'You receive nothing useful' message which is usually given when the person being read refuses to answer.

Difference between expected and actual behavior

I can't pin down the exact character limit, but it seems to be very small and impossible to ascertain when actually writing a response to a mind-reading question.

Steps to reproduce

In game, try to read someones mind with the coercion psionics faculty. Certain reply lengths will not be submitted as described above.

Specific information for locating

Length of time in which bug has been known to occur

Noticed 28/11/2021 during the scheduled high pop testing round.

Client version, Server revision & Game ID

Unknown (I forgot to check at the time, sorry)

Issue bingo

  • Issue could be reproduced at least once
  • Issue could be reproduced by different players
  • Issue could be reproduced in multiple rounds
  • Issue happened in a recent (less than 7 days ago) round
  • Couldn't find an existing issue about this
@MistakeNot4892
Copy link
Contributor

I don't believe that length should break input() like this - there are no length checks or sanitization. That failure message is also printed if you take more than sixty seconds to reply, if the user is unconscious, or the target dies. I'll slap in a commit to change as text to as message in case that helps though.

@Menkhu
Copy link
Author

Menkhu commented Dec 7, 2021

I don't believe that length should break input() like this - there are no length checks or sanitization. That failure message is also printed if you take more than sixty seconds to reply, if the user is unconscious, or the target dies. I'll slap in a commit to change as text to as message in case that helps though.

Oddly enough the window didn't seem to close in sixty seconds, but the replies were still ignored when submitted in favour of the 'You receive nothing useful' message. I didn't time it though so I could be wrong here. I'll try to check next round I can.

@MistakeNot4892
Copy link
Contributor

We can't make BYOND close an input() window, hence the sixty seconds check.

@Menkhu
Copy link
Author

Menkhu commented Dec 13, 2021

Might be reasonable to extend the check then? Almost every time I've tried to use the ability, the person on the receiving end hasn't been able to get their replies in on time, and they haven't been aware their messages weren't actually getting through, which leads to a lot of confusion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants