This repository has been archived by the owner on Apr 29, 2020. It is now read-only.
Fix the SQL for the Palborough Mines Elevator (Fixes Bug 952) #119
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Fixes long standing bug 952, which is a mission blocker: http://bugs.dspt.info/show_bug.cgi?id=952 After much debugging, I was pretty sure it was trying to move the wrong NPC, but I didn't know how to fix that. Apparently that was indeed the issue, and special thanks to forgottenandlost from the forums for responding to my debugging topic and showing me how to adjust the SQL.
takhlaq
added a commit
that referenced
this pull request
Apr 7, 2014
…r-fix Fix the SQL for the Palborough Mines Elevator (Fixes Bug 952)
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes long standing bug 952, which is a mission blocker:
http://bugs.dspt.info/show_bug.cgi?id=952
After much debugging, I was pretty sure it was trying to move the wrong NPC, but I didn't know how to fix that.
Apparently that was indeed the issue, and special thanks to forgottenandlost from the forums for responding to my debugging topic in the bugs section and showing me how to adjust the SQL.