-
Notifications
You must be signed in to change notification settings - Fork 7
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
Home SVO Response Parse Error #36
Comments
Okay, somewhere along the line the HelpGeneric.jsp one was fixed and I wasn't paying attention but the Grief Report jsp still throws errors it seems. |
GriefReport handlers we haven't looked into as far as I know. Is Grief Report a must in your use case? |
It's not a must but it's more for "completeness" sake more than anything... I know, it's weird. Anyway I kinda got the GriefReport semi-working on my fork, I mean you can't really do much on the screen but it doesn't throw an error anymore so... eh. -- still has a few weird quirks though... would be nice to see that running fully though. As I said before, I was dumb and turns out HelpGeneric was fixed post-MultiserverXP so it was kinda pointless of me to report that. You probably did fix it and I was just unaware of updates when I initially reported this. Sorry if this issue seems pointless to y'all tbh, I'll admit this is kinda pointless to ask about since most people probably are just gonna jump for the 1.8x based versions of Home anyway and I doubt anyone running a local server even cares for this functionality. |
Ahhh completeness... Okay... I will personally consider this a low-priority. |
Tested on 1.55 HDK, 1.41 Debug, and 1.00 Debug -- all of which give the same problem. Seems like every SVO-reliant version of Home return a response parse error for this file call. This also happens with the Grief Report dialog on the same versions too.
[EDIT: The HelpGeneric.jsp problem seems to have been fixed in newer versions of the SVO server but not the GriefReportWelcome.jsp one. I'm kinda an idiot for not updating and reporting this lol]
2024-03-19.06-50-24.1.mp4
The text was updated successfully, but these errors were encountered: