[Babe Runner] Doll finally Beta! ^^(and Phyton Zen...)

A minor Babe Runner update for you (yet the update is "huge" from a coding perspective):

-Nika's Doll is finally Beta!

This doesn't mean we're on an earlier stage of the game (we could've still adding her by using more "traditional ways" I'm not gonna talk about here to avoid confusing you) but it means we finally achieved a real complex way to build a doll in Phyton. Well.."we".  My buddy Xela did, and he did an awesome work. I only had the idea and gave some suggestions along the way. Just to give you a little example (for dummies, lol) of what this doll would be able to do from a coding perspective:

A doll is basically a mix of body parts: body, head, hair, limbs, clothes, gestures, etc. that have to be drawn separatedly. "Gestures" are a mix of different body parts (facial expressions, hands) changing according to the emotion you want to show...and all of that has to be "declared" into one "emotion" (i.e.: Nika_angry) from the beginning.Now. Given there are different clothing options, a single gesture would've had an hundred different variations (with coat, with shirt, naked...not to mention the colors: so one for coat_blue, one for coat_red and so on) so until now, it would've been nearly impossible to achieve other than by writing loads of useless lines of code. This doll changed this forever, meaning that it can "predict" itself, dynamically checking what your character is wearing and displaying it according to gestures! So all we have to do now is simply typing "nika_angry" and it will automatically display Nika's gesture according to the stored values for your clothing options (where "storing values" was one of my suggestions: bragging bragging! lol).

Also, there's an option to change the clothes color by adjusting RGB sliders and saving it in your wardrobe for use! ^^ 

I'm so excited about this, because it represents an HUGE leap forward for some future projects we have in mind....But I don't want to spoil them just yet. Just know this for your knowledge. 

Stay tuned, for some other major updates are in line ^^

And if you're in for some good laugh, take your time to read the "Phyton Zen", aka "words my team and I are living/coding by" (lol)

Until next time! ^^

The Zen of Python:

Beautiful is better than ugly.

Explicit is better than implicit.

Simple is better than complex.

Complex is better than complicated.

Flat is better than nested.

Sparse is better than dense.

Readability counts.

Special cases aren't special enough to break the rules.

Although practicality beats purity.

Errors should never pass silently.

Unless explicitly silenced.

In the face of ambiguity, refuse the temptation to guess.

There should be one-- and preferably only one --obvious way to do it.

Although that way may not be obvious at first unless you're Dutch.

Now is better than never.

Although never is often better than *right* now.

If the implementation is hard to explain, it's a bad idea.

If the implementation is easy to explain, it may be a good idea.

Namespaces are one honking great idea -- let's do more of those!