0 Comments
We're going to start the show with a callback to my tutorial on collecting player data where we first saw a CSVDownloader, here we see the script pop up again, and boy are we glad to see it. This script can download CSV's and convert them into any data type we desire and in this case that will be the TermData below.
Well well would you look at that! We are now approach by TermData, a cute little script that'll format our CSV data into something we can make sense of at runtime. Yes Yes Yes this is how we store the data at run-time but don't feel afraid to spice that up and edit it to fit your darkest desires!
To complete our runtime-loading-trifecta we have the final piece of the puzzle, the TranslationLoader which is ultimately responsible for sorting that CSV junk into our itsy-bitsy TermData trunk. And our first NEW NEW NEW script for this tutorial!
Hold the Phone Martha! What am I supposed to do with all this good-good data???? Well here you are handsome, a brand spanking new class dedicated to translating whatever nonsense we want to spew towards that player so we can be exactly sure they understand just how badly they got bAMBOOZE'D!
In the words of the late Henry Ford, "let's automate that shit!" This next sssssssssscript will subscribe any sister TextMesh component to a Translator delegate which can immediately propagate any changes to the user display language for the final tour de force de fucking delegate magic?? Can you say "lazy-load" five times fast???? YEah BUDdy!
The Singleton helped us to obtain any service which derived from it. However we would prefer that every script not be a singleton. Instead we can make a singleton service whose job is to find other serviced! This script is called the Service Locator. It simply caches a reference to any Monobehaviours that are requested from it.
This script ensures that the rect transform of a VerticalLayoutGroup is sized proportionate the the number of children it has.
VertLayoutScalar.cs
This script ensures that a rect transform is sized to fit within the bounds of its parent.
BoundToParent.cs
This script updates a rect transform's location to follow another transform.
FollowTransform.cs
Paste this text into the "Add a New Format" section: https://www.maximumverbosity.net/twine/Entweedle/format.js
Step 2 of 2: Create a simple dialogue parser
Now that the twine data is in a clean format we can easily write a dialogue parser for Unity. I have included my solution below which includes two files. DialogueObject.cs defines the Node, Response, and Dialogue objects which use OOP to represent the story's text and links between nodes. DialogueController.cs defines methods to direct the dialogue system as your game runs, it also has a public event that your display classes can latch onto.
Dialogue Object.cs
Note: Entweedle changed their export format since writing this tutorial so please refer to this code for the parsing method:
Dialogue Controller.cs
Good Luck!
Now you can create your own user interface to show a branching narrative in your game. I thought it would be beneficial to show you my implementation for the game 22nd Street Traffick (playable here: mrventures.itch.io/22nd-street-traffick ) DialogueViewer.cs
After all my interviews (especially the ones in which I failed) I wrote down what one would have needed to know in order to answer the questions. This guide is not a tutorial, it's not here to teach you. It's to recall topics, help memorize formulae, and maybe serve for quick reference during a phone interview or on the job itself.
Hope it helps you!! Oh and I made some videos to walk you through it if you're into that. Good luck out there.
My Offers
Zynga (software engineer, intern): Offered: $32/hr with a $1500 after-tax housing stipend Accepted: offer unaltered Tilting Point (game design, intern): Offered: $11.25/hr Countered: $20/hr with a monthly $1200 after-tax housing stipend Accepted: $14.75/hr NCsoft (software engineer, intern): Offered: $30/hr Accepted: offer unaltered Facebook (software engineer, intern): Offered: $8,000 monthly stipend with company provided housing Accepted: initial offer unaltered Hangar 13 (software engineer, intern): Offered: $25/hr with company provided housing and a two-way flight Accepted: $25/hr with a housing stipend and a one-way flight Sony Santa Monica (gameplay engineer, intern): Offered: $30.25/hr with a sign-on bonus of $5500 (pre-tax) to cover housing and relocation Countered: the above but with a GDC pass Accepted: initial offer unaltered Manticore Games Offered: $30.00/hour Countered: $30.00/hour with $2,000 after-tax housing Accepted: $32.00/hour, round-trip flights, lunches catered Epic Games, Fortnite Offered: $30/hr, round-trip flights, Housing covered, Catered Lunches Accepted: initial offer unaltered
Quick Tip: The Long One-Page Resumes should always be one page, but if you’re very close you can actually just make the page taller without folks noticing! Ingenious, right? I can use Microsoft word to extend the page size and, when it’s exported as a PDF, recruiter’s can’t tell that they scrolled the extra inch. Since people rarely print resumes these days it’s pretty hard to get caught with this trick so it’s definitely worth considering. Quick Tip: Multiple Resumes If you have multiple skills you may want to be seen as multiple applicants. In practice this might be a person, who is both a designer and engineer. In this case, they should create two resumes; one to focus on their design background and one on their engineering background. Avoid creating a resume that includes wildly different titles (for example, Matthew the artist/designer/engineer/CEO). Case Study (Before and After): Scott Below are two versions of my friend Scott's resume. This case study was a difficult challenge because Scott had a wide variety of background experiences, many unrelated to the jobs he was applying for. The key to revising this resume was nailing a specific title "Developer Relations Coordinator" and whittling down the experiences to the relevant examples. Notice how the headline of each experience clearly identifies the project, role, and date. The Profile section was used similar to a cover letter in order to frame his experiences. A bold line down the center helps the resume stand out. This resume could be further improved by making the role descriptions more concise and perhaps squeezing education into the top right if more space is required. Generally I would advocate avoiding a list of skills but it served as a nice space-filler in this case.
Case Study (Before and After): Melissa Below are two versions of my sister Melissa's resume. The focus of this case study became balancing an appealing visual design with concise text to describe her work experience. I made a particular effort to replace vague statements such as "Generated cash flow" with measured, numerical achievements such as "Increased purchase orders by 10%". Excessive detail was removed where possible and a firm title of "Junior Business Associate" was placed directly beneath her name. This title and an objective section, similar to a cover letter, provide a space for her to briefly contextualize her work experience with respect to whichever position she applies to.
Deep Dive In this video, I provide feedback on the resume and portfolio of an aspiring Gameplay Engineer.
Using Google Sheets we can store and edit our data to make live changes to our games! This tutorial covers how to download CSV's from Google Sheets and then parse them for data!
Overview In this tutorial we will breakdown an approach to downloading data from Google Sheets in a CSV format. This will allow you to update your game by simply changing a few values online! This approach will make use of three classes...
TermData
CSVDownloader
Loader
Overview
We will be covering three methods of collecting user feedback including... - Opening the user's email client - Opening a link to a Google Form for the user to manually fill out - Automatically completing a Google Form using a UnityWebRequest This tutorial include snippets from the full FeedbackCollecter.cs found here. Setup I have created a simple Unity scene for testing which includes an input field, a button, and the script we will be writing. The script has the text of the input field and the button linked to it as Serialized Fields. There is also a serialized enum so that switch between methods. 
Setup
I have created a simple Unity scene for testing which includes an input field, a button, and the script we will be writing. The script has the text of the input field and the button linked to it as Serialized Fields. There is also a serialized enum so that we can switch between methods.
For now, we don't need to worry about the last two lines, they will only be needed once we get to the Google Forms approach. the kReceiverEmailAddress should be initialized with the email address you would like the feedback emails to be sent to. This may be your email or your company's email. The following code will complete our setup including connecting several methods we will write to the submit button's onClicked event.
Opening the user's email client
For our first approach, we will use data entered into the text field to populate an email that will open on the native email app of their device. To do this, we construct a link using the information provided and we will make use of a OpenLink helper method. This method is required because we must escape space characters on iOS devices (they simply cannot open links that contain spaces, poor Apple). It would just so happen that google search results also reject spaces so I included that in the method in case you use it elsewhere in your code. (Preview of what it looks like on device: LINK).
Opening a Google Form
The email approach was great for empowering players but I have found it can sometimes be easier to sift through player data on a spreadsheet. Google Forms is an easy alternative. With the below method we can simply direct them to a form for them to fill out. This method will require that we create a Google Form on a Drive account. Then view the form and to find it's URL. That should look something like this: "https://docs.google.com/forms/d/e/1FAIpQLSchQzdbNs_wY_EWSpAtohQHRDQeliy0o6yLoRs7C5D17B-1qg/viewform" We will be using the "base URL" which is everything before the "viewform" in my case, my base URL would be: "https://docs.google.com/forms/d/e/1FAIpQLSchQzdbNs_wY_EWSpAtohQHRDQeliy0o6yLoRs7C5D17B-1qg/" Find your base URL and use it to for the kGFormBaseURL constant which we defined earlier.
Automatically completing a Google Form
The above code will successfully open a Google Form for the user to edit. But we can do better. Below is an approach that uses Unity's web request system to complete the Google Form all on its own. For this method to work we will need to find the kGFormEntryID we defined earlier. This ID corresponds to the question on the form, each question has a unique ID. To find the ID of your question, right click on the form, select "inspect page" then Ctrl+F your way to the text "entry." this text is a prefix of the ID we desire. See this .gif if you have any trouble finding it! 
Once you find the entry ID, use it to properly intialize kGFormEntryID and then the below code will be good to go! Note that is makes use of a JSON serializer. This can be useful if you want to save data this is not a string. For example, you may desire to record a player's save data or settings. By converting this data into a JSON string, we can send it along to the form. However, we need to avoid using the utility when dataContainer is actually of type string because the serializer will otherwise convert the string to simply "{}". Not very helpful!
These are only a few homebrew approaches to collecting player data, trying different approaches is the best way to find the right fit for your needs. Please consider "liking" this post or commenting on which aspects were most helpful / confusing. Your readership is very much appreciated!
|
