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

Add a basic "getting started" guide #2

Open
toolness opened this issue Apr 28, 2016 · 2 comments · May be fixed by #4
Open

Add a basic "getting started" guide #2

toolness opened this issue Apr 28, 2016 · 2 comments · May be fixed by #4

Comments

@toolness
Copy link
Contributor

Hello again!

I'm a newcomer to Unity, and I found it a little bit confusing to get The Intercept up-and-running in the Unity editor. At first I was worried that I might have imported the wrong folder, or that I was using the wrong version of Unity, or that something else had gone amiss. I did eventually figure things out, though!

Anyhow, I'm not sure how many people who are interested in Ink but unfamiliar with Unity will be looking at this project, but if you think it'd be helpful, I could try writing a very basic "getting started" guide--either as a markdown file in this repository or perhaps a wiki page.

@joethephish
Copy link
Member

Thanks for the feedback! Can I ask what specifically you had a problem with?

@toolness
Copy link
Contributor Author

toolness commented Apr 28, 2016

Sure! The first thing that gave me pause was this dialog box:

intercept-01

This made me uneasy because I wasn't sure if something might go amiss in the import process, or that perhaps I'd chosen the wrong folder to import, or something else.

Once I clicked "Continue", I expected the game (i.e., the "Demo" scene) to be visible in the editor from the outset. However, instead, the editor just contained a bare 3D scene with just a camera, so pressing "Play" didn't really do anything. I also tried choosing "Ink Player" from the "Ink" menu to see if that did anything useful, but it showed the editor widget with no Story JSON in it, so that didn't help much either. Coupled with the import warning dialog above, I thought that perhaps the project hadn't imported properly, or that I might have done something wrong.

It was only after I started digging into the "Project" section at the bottom of the editor window that I noticed the "Scenes" folder, opened it, and double-clicked on the "Demo" scene:

01-projects-panel

After that, I wanted to tinker with the ink script, which I did by opening the "Ink" subfolder in the Project window, selecting the "TheIntercept" asset, and clicking "Open" in the Inspector window:

02-edit-ink-script

I also noticed that clicking the "Play" button in the Inspector window opened the story in the Ink Player window:

03-ink-player

This made it possible for me to quickly try out changes to the game logic without having to actually play through the game, which made tinkering with the story a lot more efficient.

I also noticed that I could optionally skip the intro, which was helpful--thanks for adding that option!

04-skip-intro

@toolness toolness linked a pull request May 29, 2016 that will close this issue
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