# Text Adventure Game in Classes

Using my own version of cameron8299's Object Creation (without JS)
It's simple to understand (once you get the hang of contexts and things) but you can do whatever you want with it.

When I try it, saying Yes just makes it play music forever, while saying No starts it over again. Is there an actual story hiding in it?

The "ing" means that the creator is still making the game.

heres the current version im working on if you want to check it out. its got a little different behavior but theres now proper prototype inheritance and (better) constructors. im trying get functions to be objects with properties too but it still makes my head hurt trying to think about how thats supposed to work.

neither of these are flushed out btw. work in progress.

Given all the instances of __proto__ in your code, I take it what you mean by "proper prototype inheritance" is "just like JavaScript." Your life will be happier and deeper if you stop thinking that. :~)

but it works. what i mean is you make objects that have a prototype which you can add methods / properties to that are inherited by any instance created of that object, its like javascript yes because its the only language i know that i can use to reference to help me understand this particular style of coding. ive been exploring all kinds of different avenues and styles but javascript is something i find challenging to understand and honestly the payoff is fantastic, being able to see exactly how the process breaks down and build it back up, my confusion turns into ability and i can do things i thought only the smart people could do. im only doing it because i enjoy it so why would i want anything more? and what makes you so happy and deep? you barely dipped your toes in my water and you say it could be deeper, yeah. right. i dive in my friend.

Sure, JS works too. I was responding to

which is why I suggested that JS "prototyping" (really class/instance in disguise) is needlessly confusing. I (modestly :~) ) suggest that you'd be better off reading the explanation in the Snap! manual, and if you want more depth than that, read the Henry Lieberman paper footnoted in the manual.

daily dose of lessons on how to not be intolerant (/hj)

Gender is typically categorized into gender expression and gender identity, where expression is what you show on the outside- whether it be traditionally feminine, etc- and identity is how you feel on the inside. Neither of these necessarily impact your pronouns, although most people use pronouns that match their gender identity- for example, a trans man may use he/him pronouns. Or maybe not! Really, the only way to know someone's pronouns is to ask, and just commit it to memory.

I personally don't like prototyping but I love making classes the way ECMA intended. I made the entire morphic.js framework the way ECMA intended (or whoever designed classes in JavaScript).

You can find the non-prototyped version of morphic here.

The story is found in the Stage, if you were wondering. And I'll probably update this soon.