Update Wiki

[PopeSpaceous]

Update Wiki:
Testing Documentation: How to test
Contributing: Details on how to contribute
Setting up Development Environment: Which Unity versions are supported currently
Creating Assets: How to, guides and Info. Sprite Sheets, How to use Gimp for pixel art, Animation tree info

[saketepe]

if you can teach me i can do this. My understanding is just to download unity, then this repo and edit the files there.

[saketepe]

Where is the wiki, do i need to create one?

[PopeSpaceous]

@saketepe https://github.com/PopeSpaceous/Solitary/wiki

Let me know if you cannot access it and I'll check the permissions on it.
Thanks 👍

[saketepe]

Hi, ya i can't access it

…

________________________________ From: PopeSpaceous <[email protected]> Sent: Monday, November 5, 2018 5:49:45 PM To: PopeSpaceous/Solitary Cc: Oluwaseyi Aketepe; Mention Subject: Re: [PopeSpaceous/Solitary] Update Wiki (#122) @saketepe<https://github.com/saketepe> https://github.com/PopeSpaceous/Solitary/wiki Let me know if you cannot access it and I'll check the permissions on it. Thanks 👍 — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#122 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/Ah7O1tHrtFSa4HscQgVMDbzoslKU4rojks5usOq5gaJpZM4YHNfG>.

[PopeSpaceous]

Ok Can you check it again and if you get in please test adding/ editing.
Thanks @saketepe

[saketepe]

Hey, do you have a tot for how to install and test the code, rn i only have outlines

[PopeSpaceous]

We're working on a readme. Just trying to merge contributes branch. Will message you when its finished :)

[PopeSpaceous]

Hi, It's not merged yet, but you can see @Dragomegak 's updated readme, with contributing.
Dragomegak's Repo
If you can research and get playtest documentation on how to playtest it, that would be awesome!

[PopeSpaceous]

@saketepe We have updated the Readme for more instructions on setup, contributing etc.
Please have a look, and let me know if you have any questions.
Thanks!

[saketepe]

Hey what are your plans for there wiki? Do you want me to create a clone of the readme files, but on wiki or do you want to just link to the readme pages? Or do you want there to be something else in the wiki

[PopeSpaceous]

You could add, how to play, helpful hints. A guide to play testing (this may need some research to make a guide). And a link to the readme and contributions.

You could also find some tutorials or guides for coding in unity as resource links.

Here's what we had when playtesting. It's very rudimentary:
Instructions for Testing
Starting the Game:
To run the game, open up the downloaded Solitary folder, and click on Solitary.exe (see image below)
 
Controls:
Use either the left and right arrow keys or the ‘a’ and ‘d’ keys to move the character left and right respectively.  
Press ‘e’ to interact with in game objects like (puzzles, computers, doors, and ladders)

If you find a bug, or error:
Open the bug report document located in the same folder. 
For severity: 
•	High: If the game crashes or it causes you to not be able to play the game
•	Medium: If there is a bug that doesn’t break the game but makes the game not enjoyable to play
•	Low:  Minor bug. Doesn’t affect gameplay. Or a cosmetic issue

Steps to reproduce: 
In order to fix an issue, we have to be able to see it ourselves. Try to reproduce the bug and what steps you did to cause it

Expected Results vs Actual Results
An Expected vs Actual result would be something like:
Ex. Jumping off a platform onto the ground. Expected: Player stops vertical movement when they reach the floor. Actual: Player continues through floor and clips through it. 

Images:
A picture is worth a 1000 words. (A video is worth even more)
If possible attach a picture of the bug to the report. This greatly helps the debugging and patching of the game. Use the link for instructions on how to use the Windows Snipping Tool.

[saketepe]

Thanks This is a good idea

…

________________________________ From: PopeSpaceous <[email protected]> Sent: Thursday, November 15, 2018 11:24:11 AM To: PopeSpaceous/Solitary Cc: Oluwaseyi Aketepe; Mention Subject: Re: [PopeSpaceous/Solitary] Update Wiki (#122) You could add, how to play, helpful hints. A guide to play testing (this may need some research to make a guide). And a link to the readme and contributions. You could also find some tutorials or guides for coding in unity as resource links. Here's what we had when playtesting. It's very rudimentary: Instructions for Testing Starting the Game: To run the game, open up the downloaded Solitary folder, and click on Solitary.exe (see image below) Controls: Use either the left and right arrow keys or the ‘a’ and ‘d’ keys to move the character left and right respectively. Press ‘e’ to interact with in game objects like (puzzles, computers, doors, and ladders) If you find a bug, or error: Open the bug report document located in the same folder. For severity: • High: If the game crashes or it causes you to not be able to play the game • Medium: If there is a bug that doesn’t break the game but makes the game not enjoyable to play • Low: Minor bug. Doesn’t affect gameplay. Or a cosmetic issue Steps to reproduce: In order to fix an issue, we have to be able to see it ourselves. Try to reproduce the bug and what steps you did to cause it Expected Results vs Actual Results An Expected vs Actual result would be something like: Ex. Jumping off a platform onto the ground. Expected: Player stops vertical movement when they reach the floor. Actual: Player continues through floor and clips through it. Images: A picture is worth a 1000 words. (A video is worth even more) If possible attach a picture of the bug to the report. This greatly helps the debugging and patching of the game. Use the link for instructions on how to use the Windows Snipping Tool. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#122 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/Ah7O1ujSx6_hvz7tk6gqpV4xnL6knSZaks5uvb9bgaJpZM4YHNfG>.