A pure baby “BHAHAHA PENNY IS A DOG AT HEART. #opossum #possum #cute #howto #travel #funny”

Made with Vine
Winter Greetings in Russian

Here are a few phrases that you may use for your holiday greetings when talking or chatting with your Russian friends:

  • С Новым годом! - lit. (My greetings to you) with the New Year!, Happy New Year!
  • Счастливого нового года! - Happy New Year!
  • Пусть новый год принесёт тебе (Вам for formal, вам for plural) счастья, удачи, радости, здоровья, любви, процветания, успехов - May the New Year bring to you happiness, good luck, joy, good health, love, prosperity, success… Mind you, all the wishes should be in Genitive
  • Счастья, улыбок и радости в новом году - Happiness, smiles and joy in the New year! (again, the wishes should be in the Genitivee case).
  • С Новым годом и Рождеством! - Happy New Year and Christmas! If your friends are religious, you may modify to:
  • С Новым годом и Рождеством Христовым!
  • Со светлым праздником Рождества Христова! - lit. (My greetings) with the light (=holy) day of the Birth of Christ!

Just a reminder: the Russian orthodox church celebrates Christmas on January 7th.

Update: Sure, all the wishes are in Genitive! Sorry for the confusion!

How to find your Totem Animal

Everyone has an animal, bird or fish which holds a special meaning for them. This is not necessarily a pet or even a domestic animal; it could be foreign or even mythical

1. Take a walk in the woods just before dusk. Take the time to look at the trees and plants, to inhale the scent of the woods and listen to the sounds around you. 

2. Find an old tree and sit down beneath it. Close your eyes and lay your hands flat on the soil on either side of you and take a few deep breaths. 

3. Ask the Goddess to send you your Totem animal. 

4. Open your eyes and pick up the first thing you see lying on the ground near you. Take this home and place it under your pillow for three nights and your Totem animal will come to you in your dreams.

5. When you know what your Totem animal is, remember to look out for it in the world around you and to acknowledge this gift of the Goddess each time you see it


Everyday Goth Makeup Tutorial 2

To mark 3 years on YouTube (I know right?) I recreated my first ever video, only much better! :)

How Cutscenes Work in Wandersong

Wandersong’s a musical adventure game about a bard, where you use singing to solve the world’s problems. It’s made in GameMaker Studio. And it has a big emphasis on story, with a lot of characters and unique scenes. People often ask me how I implement all that behind the scenes, so I figured I’d share my tools a bit.

(Above: a typical conversation, and some of the code that drives the scene)

The basics are pretty straightforward. There’s a cutscene manager objects who hangs out invisibly in every screen of the game. When one of the special cutscene scripts is called, it passes instructions to the cutscene manager, who always keeps a list of instructions running. And whenever the cutscene instruction list has anything in it, the cutscene manager broadcasts that a cutscene is happening, and processes the instructions in its list one by one, until they’re done.

The most important detail of this implementation, I think, is that it lets me write cutscenes inline with the rest of the game logic, and it’s all very natural and fluid, so I can focus on being creative and making it as I go. Other games will often separate the writing and scene stuff into separate files or systems, like an XML data file or a LUA interpreter or something, so that it’s easy to collaborate with a writer without them having to deal with programming, and it can be exchanged later with translated versions. But since I’m also doing all the programming and animation anyway, it’s easier for me to put it together all at once. I’m pretty far along on a solution for translations, too, but that’s for another time…

I’ll share some nitty-gritty on how I make it work specifically in game maker below.

Here’s a typical cutscene script, marked up a bit. All of them follow this structure, which, right out of the gate, is pretty hacky, heh heh. There’s actually two completely different uses for each script, one for when it’s used by the scene manager (red), and one for when it’s used by anything else (blue). The blue part is the one that happens first, so I’ll start there.

The blue part is basically identical in every cutscene script, actually, and I always make a new scene script by duplicating an old one because of this. First, it adds the name of the current script to the objSceneManager’s “scene” list. In Game Maker the name of resources like scripts, sprites, sounds etc. are automatically special words that let you point to them (for example, when you want to play a sound file, typically you’ll tell it the name of the sound so it knows which one to play). So the script basically adds itself to a list somewhere.

Second, it makes a new list that contains all of the “arguments” passed to it. This script is for setting the position of an object during a cutscene, and I give it the name of an object, an x position and a y position… so all those values are stored into a list, and then it adds that list to objSceneManager’s “scene_args” list. Lists of lists might sound kind of silly, but this game is full of them behind the scenes, and they also excite me in ways I don’t fully understand.

This little pile of code is the key that makes the rest of it run, basically. The line underlined in red is the big one. The scene manager tracks where it is in the cutscene with a variable called “scene_moment,” and every frame it looks at that spot in the scene and scene_args lists and runs all the instructions left there. The arguments we passed to the scene initially are stored in lists, and we pass those lists back to the script when we run it from the scene manager. Scene scripts when run from the scene manager always return a true or false, to let it know if they finished their job or not. The scene manager runs them from a “while” loop, which goes forever until it gets a “false” from one of these or runs out of them. The blue section shows what happens when it runs dry… basically it just clears and resets everything.

Back to here, now, looking at the red section… this is how it runs from the scene manager. Instead of looking at arguments, we look at the list passed to us in argument[0], and evaluate the contents of that list like arguments instead. Then we do a little code and return true. Actions that take time or need input, like a textbox or a “Wait for x amount of time” command, will return false until their conditions are all met, at which point they return true. This way I can have many actions parsed in the same frame, like a camera movement and a sound being played, and other times I can create timings by adding in pauses and stuff.

Ta-da! That’s it. I hope it wasn’t too hard to follow. I’ve done a number of games with lots of text and scenes before, but this basic system was a new idea for this game and it’s been by far the most useful and flexible system I’ve been able to work with. Feel free to lift the structure wholesale and make sweet cutscene-filled games with it. And also, feel free to send me questions if I wasn’t clear enough about something. 


A small step-by-step tutorial on hoe to paint hair!
#hair #howto #drawhair #hairtutorial #painthair #howtodraw

Made with Instagram

Girls be like watching novela.

Made with Vine

How to print etching…. Working with @satellitepress for this coming autumn #etching #acquaforte #print #printing #howto #howtoprint #gaia #moreno #baldelly #ful

Made with Instagram