-
Notifications
You must be signed in to change notification settings - Fork 22
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
Allow insecure requests #1
Comments
Addendum: Does the game expect a secure request in response to the insecure request? Is the game flexible enough to handle insecure responses all the time, and likewise for secure responses? |
fluofoxxo
added
good first issue
Good for newcomers
help wanted
Extra attention is needed
labels
Aug 9, 2019
Addendum: Currently insecure requests cause panics due to the lack of an IV. Solve this. |
Tackling when I get a chance. |
fluofoxxo
removed
good first issue
Good for newcomers
help wanted
Extra attention is needed
labels
Aug 10, 2019
fluofoxxo
pushed a commit
that referenced
this issue
Oct 27, 2019
Added event IDs for event characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Insecure requests are sent at least by /Battle/ requests. Sate the ability to utilize the data sent by these requests.
Notes:
secure
= 0 when the request is insecure.param
is URL escaped when insecure.key
= nothing when insecure.The text was updated successfully, but these errors were encountered: