Blog

Naming Creatures

I opened Lasha's drawings, and a banana-dog hybrid was smiling at me. I had seen sketches of the banana-dog before, but this was my first time seeing it in color. It had brown speckles all over it, and looked like a perfectly ripened banana. (This creature sparked an office debate on what constitutes a "perfectly ripe" banana.) The first word that came to my mind was "Mushy", and Musha was born.

I imagined groups of these banana-dogs roaming dingy alleys looking for tasty treats (they hatch from Trash Eggs, after all). After a successful search, what better place to nap than under those dryer exhaust vents? After some feedback from Dyala, we agreed that the lint from the dryer vent would get stuck to the Musha's mushy tushes. We decided that Mushas could reasonably sleep under any type of vent, and removed the "dryer" detail. (Although I still like to imagine them making blankets out of dryer lint.)

As I started looking at the other Trash Egg creatures, I knew I wanted their names to create a sense of connectedness. I pulled open an image of a bat-like creature that also resembled an umbrella. I remembered a story my boyfriend (who is obsessed with cars) had told me. Lamborghini once made a sports car called the "Murciélago". The car was named after a famous Spanish bull, who was, incidentally, named "bat". "Ah", I remembered, "in Spanish, Murciélago means bat". Perfect! Murciela had been named, and I had a theme.

Have you ever seen an orange bull? Me neither.

Have you ever seen an orange bull? Me neither.

Knowing that I wanted the other creature's names to also begin with "Mu" helped direct the process. I opened up a picture of a creature made from cardboard, and its stance immediately reminded me of a Komodo Dragon. Easy enough – Mumodo it is!

Next up was a rodent creature made out of a black trash bag. I was stumped for a bit! After some brief research on Wikipedia, however, I learned that the scientific family name for rats is "Mureoidea", which just happens to begin with "Mu".  I merged the word "rat" more clearly into the name, and ended up with Muratia. It was easy to imagine this fancily named creature sifting through garbage, searching for gems and trinkets.

I was now staring at an image of a green slime creature. The green was such a nice bright color – not quite the "sewer sludge" you see in the movies, this creature was more of a "radioactive ooze". I thought of scientists mixing and churning modern chemicals into new products. I recalled my middle school science class, where we made oobleck, a cornstarch and water mixture with interesting properties. From here, it was easy to attach the "Mu" to create Mubleck.

Lastly, it was time for the creature I had been purposely avoiding. An adorable pink swirl that resembled the poo emoji, but somehow cuter. I wanted to give this creature a good name, and not cast it to the side like, well, poo. After some discussion with the team, we agreed that we should let the creature shine, instead of trying to hide what it was. Without much delay, Mupupu was the final, and arguably most sincere, Trash Egg creature to be named.

Creating names and descriptions for 'Egg!' can be a lot of fun. When tasked with writing, we often pull from various sources – memories, anecdotes, and a little bit of research. Because of this, designers get to add a lot of their own personality and voice into the game. You may notice that each set of creatures sounds like a different person, or that they came from a different place. This is just one of the many ways we keep the world of 'Egg!' exciting and interesting!

- Brendan

Mission Report: Writing A Bug

Have you ever played this awesome game where a guy in a green tunic travels around a kingdom called Guyrule (Not actual name) with this amazing blue shield and sword? I did! Did you ever come across this one problem in said game where you would go talk to a specific character that would give you a set of 3 missions. If you followed the list in order and returned to that same character, your game data would be corrupted, making that 5 hours of re-spawning game play go down the drain.

Welp! There goes 5 hours...

Welp! There goes 5 hours...

Oh hoho, I did and let me tell you I wasn’t too pleased with the creators. But why would I bring an issue you may or may not have heard of? Well, dear children of Eggverse, you may have encountered a issue similar in another game. Maybe something that was clearly broken, awfully implemented or even upsetting to play?

So now I ask you this important question. If you found an issue like the one I just described, how would YOU go about reporting the issue to the creators of the game? That’s where writing a bug up comes in. As QA testers, we are tasked with finding and writing up every issue we can find in a game in order to help developers. This helps them make the necessary fixes or changes so the game doesn’t break or look bad. QA needs to find, locate, and instruct the programmers on how to find the issue on their own while we continue to find more bugs. We are like mission control, we give out the coordinates and the programmers go out and diffuse the bomb. If the code a programmer wrote does not work as intended, we send back the issue in order for them to work on another fix.

Now writing up a bug may sound like the simplest thing to you. Total walk in the park right? Alright, let me test you on your assumption. In 8 steps, could you walk me through how to make a peanut butter and jelly sandwich? Is your first step to go buy the ingredients or take the bread out? Wrong! (There’s the door, see yourself out)

Don't forget to say Goodbye!

Don't forget to say Goodbye!

You see, you already have all the supplies in front of you. Why would you waste a step on telling someone who already has the set up to make this delicious PB and J sandwich to go buy bread?

Lets Jelly Jam!

Lets Jelly Jam!

Each and every issue that we write into our database consists of 3 major things.

* Summary

* Description

* Steps to Reproduce

Step 4 is mandatory!

Step 4 is mandatory!

All three are important. What is most important is to write a clear and detailed report on what it is that was found. We write up issues with the most detailed amount of steps and information to help our programmers resolve the issue that we encounter. And sometimes we add a picture of the issue for good measure. (That’s because QA doesn’t want to come off as crazy liars when the programmers can’t reproduce the issue. We have PROOF, we tell you! PROOF!) We do it to not only help them out, but also so when we go back in to check if the issue is fixed we aren’t confused on what our team member found.

Take a picture, it last longer!

Take a picture, it last longer!

So you can bet that when a bug like “A crashed occurred when tapping a button in room” is submitted it drives QA bonkers. Like, what room where you in? Which button did you push? What were you doing before you went into the room? Is it a soft crash or a hard crash? Did it delete your file? Did this happen before or after you got the Hylian Shield because if it happen after, you just spent 5 whole hours of boss battles for nothing! NOTHING! (Sorry, it gets me every time)

Details! It’s all about the details. You wouldn’t tell a cop that someone stole your awesome PB and J sandwich without telling them it was a large purple dinosaur with some whiter than white teeth and green spots on its back. How would justice be served!? Justice, to that beautifully made PB and J!

So remember kids, when reporting an issue, it’s always important to spread the peanut butter before the jelly. OH! And the details, the details are also important.

Enjoy my child-like PB and J! (Katie had better ones)

Enjoy my child-like PB and J! (Katie had better ones)

 

- Cass