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

Make mission_id 78 solvable #17077

Closed
wants to merge 1 commit into from

Conversation

Projects
None yet
5 participants
@mlangsdorf
Copy link
Contributor

commented Jun 6, 2016

Change mission_id 78 from "Find a Book" to "Find the Zombie Guide",
add quest dialog, and make it solvable with a copy of the Zombie
Survival Guide.

Make mission_id 78 solvable
Change mission_id 78 from "Find a Book" to "Find the Zombie Guide",
add quest dialog, and make it solvable with a copy of the Zombie
Survival Guide.

@mlangsdorf mlangsdorf closed this Jun 6, 2016

@mlangsdorf mlangsdorf reopened this Jun 6, 2016

@mlangsdorf

This comment has been minimized.

Copy link
Contributor Author

commented Jun 6, 2016

This address the bug reported here
#17077

@i2amroy

This comment has been minimized.

Copy link
Member

commented Jun 7, 2016

The best way to handle issue fixing is to edit the original post to put in the exact phrase:
"fixes #issue_number_here"

Which will ensure that if your pull request gets merged that it automatically closes that issue. Elsewise we have to find that issue and close it manually.

@mlangsdorf

This comment has been minimized.

Copy link
Contributor Author

commented Jun 7, 2016

On Tue, Jun 7, 2016 at 2:50 PM, Christian Buskirk notifications@github.com
wrote:

The best way to handle issue fixing is to edit the original post to put in
the exact phrase:
"fixes #issue_number_here"

Does the "original post" mean the thread here:
http://smf.cataclysmdda.com/index.php?topic=11198.0

or my pull request here:
#17077

or something else?

And how do I get the issue number?

Which will ensure that if your pull request gets merged that it
automatically closes that issue.

I want to contribute as usefully as possible, I'm just not at all familiar
with your
workflow.

Thanks for the pointers.

--Mark Lagnsdorf

@Zireael07

This comment has been minimized.

Copy link
Contributor

commented Jun 8, 2016

#17077 is this very PR we're discussing, I think you made a typo.
You were told to put the bug issue number in the PR title.

@mlangsdorf

This comment has been minimized.

Copy link
Contributor Author

commented Jun 8, 2016

I will edit the PR title to add the bug issue number but I don't know the bug issue number. How do I get that information?

@Coolthulhu Coolthulhu self-assigned this Jun 8, 2016

@Coolthulhu

This comment has been minimized.

Copy link
Contributor

commented Jun 8, 2016

I can't test it, NPCs with this mission don't seem to want to give it. Mission code is a major mess so there's a chance missions are sorted by ID, need extra changes or something like that.

@Coolthulhu Coolthulhu removed their assignment Jun 8, 2016

@mlangsdorf

This comment has been minimized.

Copy link
Contributor Author

commented Jun 9, 2016

I branched my tree off of commit f9fa31f and at that point it was possible to test the mission using the debug key. I'm not sure what happened since then.

@BevapDin

This comment has been minimized.

Copy link
Contributor

commented Jun 10, 2016

Well, the NPC gives out the mission once they follow you. And the mission itself works fine.

@@ -2496,6 +2496,32 @@ Before we get into a major fight just make sure we have the gear we need, boss."
}
break;

case MISSION_FIND_ZSG:
if( state == "TALK_MISSION_DESCRIBE" ) {
return _("I've can an idea about how to improve our chances of surviving");

This comment has been minimized.

Copy link
@BevapDin

BevapDin Jun 10, 2016

Contributor

"can an idea"? Maybe "I've an idea..." - the "can" seems wrong there. There seems to be a period missing at the end of the sentence.

This comment has been minimized.

Copy link
@mlangsdorf

mlangsdorf Jun 10, 2016

Author Contributor

Thanks for the feedback.

I've made the changes in my local tree to fix those two typos - how do I go about publishing them? Do I amend the commit and push the fix back to github or something else? I checked
http://smf.cataclysmdda.com/index.php?topic=1063.0 but it didn't address the issue of making changes to your code after submitting the pull request.

This comment has been minimized.

Copy link
@Zireael07

Zireael07 Jun 11, 2016

Contributor

You push to your branch (mlangsdorf:fix_mission_78) and this PR automatically gets updated.
Pro tip: use a GUI client for git stuff, such as SourceTree or GitHub for Windows.

@mlangsdorf mlangsdorf closed this Jun 13, 2016

@mlangsdorf mlangsdorf deleted the mlangsdorf:fix_mission_78 branch Jun 13, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.