In the beginning, there was That Which Is, and That Which Is Not. That Which Is came to realize itself, and took the name Uhl and called itself the Sea, and That Which Is Not named itself Yaw and called itself the Sky. The Sky blew above and the Sea flowed below, and where the two met a great froth formed. The froth churned and bubbled, and from it came a great green mass that named itself Ur, and was called Life by Uhl, the Sea, and Yaw, the Sky. Ur made it known to Uhl and Yaw that it was not born of them, but it had always existed, though without form.
Thus it was that Ur floated on top of Uhl and beneath Yaw, and as Ur's body lived, so to did it die, and sink into the depths of the Sea. And so, as Life was given body from the froth where the Sea met the Sky, and the death of this body created a great mound within Uhl, until it pushed Ur aside and passed from Uhl into Yaw. The Sky saw this and called the bodies Earth, and as Earth came into contact with Lice, it began again to live, and named itself Dou.
So it was that Uhl flowed and Yaw blew, and that from their froth Ur took body, and as that body lived and died it gave shape to Dou, and Dou continued to grow. As Dou grew wider, and taller, there ame to be parts of the Earth where Uhl could no longer reach, and so Uhl asked Ur what these parts of the Earth were like. Ur agreed to look, and crawled onto Dou, and thus Life spread across the Earth. As there was life, there was death, and where Life became death without the touch of the Sea, a new thing came to be. It burned, and scorched Dou's body, causing great pain, and so Dou begged the Sea and the Sky for help. So the Sky picked up great armfulls of the Sea and poured it onto the Earth, and when this water, now separated from Uhl, touched Ur it sprang to new life, and named itself Ber, and it was called Rain.
As Ber poured down, there came a great cry as the heat recoiled in pain. The heat named itself Man, and begged for the Rain to end. Dou refused, furious over the pain it had felt, but Uhl pointed out the pain of having the Earth inside of the Sea, and Ur the pain of the death that gave the Earth shape. So Dou relented, and Man became called Fire. Dou's heart hardened with resentment, but the Earth in time realized that Fire could not exist without the Earth to separate it from the Sea. Thus the Earth became sympathetic towards Fire, and separated from it's hardened heart, calling it Metal, and upon being separated from Dou it came into new life, naming itself Dai.
Man was greatful for the mercy of Dou, and yet worried that he could again grow wild and beyond control; and so, he dug great trenches, and asked Uhl and Ber to fill them. Ur, being curious, moved to see these new things, and called them River, and as they touched Life, they became aware and took the name Ban.
Thus it was, that the Sky blew above, and the Sea flowed below, and the Earth rose from the depths, and Life was given body and crawled from the Sea to the Earth, and Fire was born of death without water, and Rain and River were made to prevent the Fire from destroying all, and anger became Metal in the heart of the Earth. This, is how the world was formed.
6/10/2013
5/31/2013
the women
Larich - Short Soldier
Larich is a young (mid forties) Dwarf woman, actually somewhat tall for her kind, with a high pitched voice and a somewhat childish attitude. Her mellow nature and friendly demeanor make her friends easily, a somewhat unusual trait, given that most adventurers are at best a bit rough around the edges. Her size, voice, and attitudelend to most people (deliberately or otherwise) treating her like a kind of little sister. She plays this up at times, but is every bit as capable as any other adventurer. Larich was brought to the world of quests and conflict by equal parts wanderlust and being kicked out of Dwarfhome for refusing to choose a profession and stick with it.
While Larich is friends with pretty much everyone in the guild, if she takes a particular shine to the player she'll follow them around when not otherwise busy. While sometimes annoying she makes an effort to be helpful when she can; sparring with the player, helping them study, or teaching them about the six different grades of granite recognized by the Dwarven Masonry Union. If this develops along more romantic lines, Larich attitude towards the player is best described as puppy love.
Larich's story is about how - or even if - she decides to balance the serious with the silly, whether she 'grows up' or not. It also deals with how outward appearances shape how people interact, intentionally or otherwise.
Caroline - The Amazon
Caroline is a relatively normal Plainsdweller woman thats simply tired of life on her family farm. Fortunately, even a relatively normal Plainsdweller woman is still seven feet tall and nearly three hundred pounds. Unlike most Plainsdwellers, though, rather than being rather humble about her strength she embraces it. She's not the best fighter or the quickest learner, but her work ethic and determination to see her choise through more than make up for it.
As with almost any Plainsdweller, Caroline values honesty and reliability (humility, not as much). If the player becomes friends with her they can rely on to go through Hell and back, so long as they carefully stoke her ego and make her feel like a hero. Similarly, the key to ensnaring her romantically is to flatter her and keep her feeling like she's in control (or at least, allow her the space to outwardly say that she is).
Caroline's story revolves around the purpose of power, and to what end Caroline uses hers. She can end up either as an example of exceptionalism (if she simply works to become the best she can and thinks of power as it's own reason), as a leader (if she uses her power to improve her own social and economic standing), or as a hero (if she uses her power to help others).
Esther - Queen of War
The middle-aged widow of an adventurer, Esther bicked up basic combat skills from her late husband and developed a desire to see the continent, intruiged by the mementos and stories he brought back from his travels. As the daughter of a wealthy Doren merchant, she has a refinement and style that give her a rather regal bearing relative to the sort that usually become adventurers, earning her the nickname 'Queen of War'. In spite of her relative newness to the profession, Esther holds a surprisingly large body of knowledge, thanks to her relationship with her late husband.
If the player befriends Esther she becomes a sort of advisor. She's had enough exposure to the upper crust of her parent's world to understand the mindset behind the type that generally fund adventurers, and enough contact with adventurers to understand what drives them. If pressed, she reveals the player reminds them of one of her husband's old friends. As a romantic interest, Esther has the same feckless attitude towards sex shared by many adventurers, she is more reserved about holding a more serious relationship.
Esther's story deals heavily with the Adventurer's Guild and how such a powerful entity fits into the political dynamic of a fantasy world. It deals with how the Guild maintains some degree of neutrality, how it reacts in times of outright war, and when different buyers pit adventurers against each other.
Kelson - White Rose
Kelson is a young Ratkin woman with creamy white fur, which has earned her the nickname 'mouse' among those she grew up with. This name does not please her. As a result she's become rather defensive and hot-headed (partly to counter the weak image that the name carries n her mind). Even so, when she does reign in her aggression the name rather fits - she's a genuinely sweet and gentle girl with those she's comfortable around. Kelson joined the Adventurer's Guild simply as a way of making extra money where she could.
Having come from a family and culture where reliance on others is tantamount to the survival of the group, Kelson can be relied on to do just about anything if the player befriends her. However this works both ways - a player that refuses one of her requests will quickly find her becoming distant. As a romantic interest, Kelson takes the same kind of ultra-aggressive childishness you might see on a playground. She does make her interest in the player very clear however, coming across less tsundere and more crazy bipolar girlfriend.
to clarify since i didn't make it clear in the last post;
Pascavis - romance is open to females/herms
Caspar - romance is open to all
Rex - romance is open to females
Joachim - romance is open to females/herms
(there will be other male homosexual romance options available - a dwarf in the 'bear' mould and a sort of effeminate goblin guy)
Larich - romance is open to all
Caroline - romance is open to men/herms
Esther - romance is open to all
Kelson - romance is open to all
the decision to open more women to same sex relationships is very simply because in the polls i've had up in the past, more people stated that they played women (and herms), and more people expressed interest in fem/fem and fem/herm relationships than man/man and man/herm.
naturally all of these characters are going to be added rather slowly once the game proper starts getting out. probably going to start with kelson and rex, adding the rest of the core eight, and then moving on, adding characters as their locations start coming up. also worth noting is that these are all notable characters, intended to have romantic encounters beyond simple sex, and all capable of joining your party to fight.
Larich is a young (mid forties) Dwarf woman, actually somewhat tall for her kind, with a high pitched voice and a somewhat childish attitude. Her mellow nature and friendly demeanor make her friends easily, a somewhat unusual trait, given that most adventurers are at best a bit rough around the edges. Her size, voice, and attitudelend to most people (deliberately or otherwise) treating her like a kind of little sister. She plays this up at times, but is every bit as capable as any other adventurer. Larich was brought to the world of quests and conflict by equal parts wanderlust and being kicked out of Dwarfhome for refusing to choose a profession and stick with it.
While Larich is friends with pretty much everyone in the guild, if she takes a particular shine to the player she'll follow them around when not otherwise busy. While sometimes annoying she makes an effort to be helpful when she can; sparring with the player, helping them study, or teaching them about the six different grades of granite recognized by the Dwarven Masonry Union. If this develops along more romantic lines, Larich attitude towards the player is best described as puppy love.
Larich's story is about how - or even if - she decides to balance the serious with the silly, whether she 'grows up' or not. It also deals with how outward appearances shape how people interact, intentionally or otherwise.
Caroline - The Amazon
Caroline is a relatively normal Plainsdweller woman thats simply tired of life on her family farm. Fortunately, even a relatively normal Plainsdweller woman is still seven feet tall and nearly three hundred pounds. Unlike most Plainsdwellers, though, rather than being rather humble about her strength she embraces it. She's not the best fighter or the quickest learner, but her work ethic and determination to see her choise through more than make up for it.
As with almost any Plainsdweller, Caroline values honesty and reliability (humility, not as much). If the player becomes friends with her they can rely on to go through Hell and back, so long as they carefully stoke her ego and make her feel like a hero. Similarly, the key to ensnaring her romantically is to flatter her and keep her feeling like she's in control (or at least, allow her the space to outwardly say that she is).
Caroline's story revolves around the purpose of power, and to what end Caroline uses hers. She can end up either as an example of exceptionalism (if she simply works to become the best she can and thinks of power as it's own reason), as a leader (if she uses her power to improve her own social and economic standing), or as a hero (if she uses her power to help others).
Esther - Queen of War
The middle-aged widow of an adventurer, Esther bicked up basic combat skills from her late husband and developed a desire to see the continent, intruiged by the mementos and stories he brought back from his travels. As the daughter of a wealthy Doren merchant, she has a refinement and style that give her a rather regal bearing relative to the sort that usually become adventurers, earning her the nickname 'Queen of War'. In spite of her relative newness to the profession, Esther holds a surprisingly large body of knowledge, thanks to her relationship with her late husband.
If the player befriends Esther she becomes a sort of advisor. She's had enough exposure to the upper crust of her parent's world to understand the mindset behind the type that generally fund adventurers, and enough contact with adventurers to understand what drives them. If pressed, she reveals the player reminds them of one of her husband's old friends. As a romantic interest, Esther has the same feckless attitude towards sex shared by many adventurers, she is more reserved about holding a more serious relationship.
Esther's story deals heavily with the Adventurer's Guild and how such a powerful entity fits into the political dynamic of a fantasy world. It deals with how the Guild maintains some degree of neutrality, how it reacts in times of outright war, and when different buyers pit adventurers against each other.
Kelson - White Rose
Kelson is a young Ratkin woman with creamy white fur, which has earned her the nickname 'mouse' among those she grew up with. This name does not please her. As a result she's become rather defensive and hot-headed (partly to counter the weak image that the name carries n her mind). Even so, when she does reign in her aggression the name rather fits - she's a genuinely sweet and gentle girl with those she's comfortable around. Kelson joined the Adventurer's Guild simply as a way of making extra money where she could.
Having come from a family and culture where reliance on others is tantamount to the survival of the group, Kelson can be relied on to do just about anything if the player befriends her. However this works both ways - a player that refuses one of her requests will quickly find her becoming distant. As a romantic interest, Kelson takes the same kind of ultra-aggressive childishness you might see on a playground. She does make her interest in the player very clear however, coming across less tsundere and more crazy bipolar girlfriend.
to clarify since i didn't make it clear in the last post;
Pascavis - romance is open to females/herms
Caspar - romance is open to all
Rex - romance is open to females
Joachim - romance is open to females/herms
(there will be other male homosexual romance options available - a dwarf in the 'bear' mould and a sort of effeminate goblin guy)
Larich - romance is open to all
Caroline - romance is open to men/herms
Esther - romance is open to all
Kelson - romance is open to all
the decision to open more women to same sex relationships is very simply because in the polls i've had up in the past, more people stated that they played women (and herms), and more people expressed interest in fem/fem and fem/herm relationships than man/man and man/herm.
naturally all of these characters are going to be added rather slowly once the game proper starts getting out. probably going to start with kelson and rex, adding the rest of the core eight, and then moving on, adding characters as their locations start coming up. also worth noting is that these are all notable characters, intended to have romantic encounters beyond simple sex, and all capable of joining your party to fight.
5/30/2013
the guys
Pascavis - Son of Doren
Pascavis is a Imperial master swordsman, recently retired from the Doren guard. After years of hard work and climbing ranks, he began to feel a dissatisfaction with his work. His settled on the idea of becoming an adventurer, always having been intruiged by the strange wanderers that he met so often during his work, usually getting into some sort of trouble. All the same, he sees the Guild's training process as a necessity, because while he can hold his own against any of the combat trainers, his wilderness survival skills were almost nonexistent, having spent his entire life in the city. While constant association with the city's criminal element has hardly left him naieve, he is somewhat ignorant of life outside the city's well-ordered and civil culture.
As a friend, Pascavis is something of a big brother, taking a somewhat protective mentor role if they're weaker than him and a acting as a staunch ally and loyal friend if they're equally matched or stronger than him. As a romantic interest, Pascavis is somewhat awkward, his life in the city guard having left him with time for only a few short relationships. He tends to follow the player's lead, rather than take the initiative on his own. Pascavis has no romantic interest in other men.
Pascavis's story arc revolves around the disconnect he feels between his strength and his possession of it. He is a fantastic fighter, but has always lent his sword to the causes of others, and never his own, to the point where he isn't even sure if he has a purpose on his own.
Caspar - The Hero Born
Caspar is a Highborn from Knell, seeking to become a famous adventure - revered, respected, and feared. His life, to this point, has been spent working towards this goal; he has studied swordsmanship, law, etiquette, court politics, learned how to survive in the wilds, repair his armor and weapons, and anything else he could possibly imagine might be worthwhile to know when questing for fame and glory; everything, that is, except how to be a figure worth admiring. Caspar is incredibly competitive but somewhat good natured about it; in truth, he's too focused on himself to consider actually trying to sabotage anyone else.
Caspar sees the potential the player has if befriended, and quickly seeks to ensure his own greatness by associating himself with the player. The two train together and Caspar makes his loyalty known by deeds as well as words, but all the same, his drive to compete sets him up as a sort of rival. Caspar can (and will) fall in love with any player that happens to strike his fancy, male, female, or otherwise. As in everything else, he tends to be somewhat demanding and self-centered.
Caspar's arc explores the relationships between fame, strength, and social power. If such a book had been written in this world, Caspar would consider 'The Prince' to be his bible.
Rex - The Unfortunate Giant
Rex is a Lizardkin born abnormally large. He stands as tall as an Imperial, with a slim and powerfully muscled body that comes almost without effort. Such individuals are not entirely unheard of among the Lizardkin, but Rex lacks the thick armor-like scales that usually come with his size. The combination of size and a distinct, almost draconic, appearance generally means those like Rex are heralded as great leaders, but his utterly mundane scales leave him stranded somewhere in the middle. Unable to command the respect needed to lead but never quite fitting in among the common people, Rex left the Sun Coast to seek his fate as an adventurer.
Rex and the player can easily become friends simply if the player accepts Rex as he is. Rex, for his part, feels some sort of deep strength in the player, some ethereal quality that seems to make them a born leader. His curiosity about the player, bordering sometimes on being awestruck with them, seats him into the role of a younger sibling. As a romantic interest, Rex finds himself drawn to this same ethereal quality. He sees a certain sort of premeditation in the way the player moves and speaks that utterly enchants him.
Rex's story centers around how he chooses to deal with the situation of his unique birth. It explores ideas surrounding tradition, social expectation, and personal desires.
Joachim - The Killer
Joachim is a calm and controlled older man that, like most Foresters, prefers to remain quiet when not directly spoken to. What makes him unusual is his temper. Whether because of his (rumored) Orcish heritage, some kind of disorder, or an outright curse, Joachim has a propensity to fall into a blind, unthinking rage when he feels his life is at risk. Joachim has joined the adventurer's guild after several years living as a near hermit, having finally decided to try and find something - anything - that can help him learn to control himself.
Joachim, regardless of whatever kind of relationship he has with the player, remains somewhat distant from them. As a friend, Joachim seems to take some small comfort in the player's almost cavaleir willingness to spar with him, to the point where he questions if they even believe his rages are real. As a romantic interest, Joachim is somewhat more complex; he is a bit of a romantic and helpless to the urges of his heart, but his sense tries to keep him from getting too close to anyone, lest he lose control at a bad time.
Joachim's arc examines the unavoidable violence that combat always entails,and where the line is drawn between a civil fight and the sort of tooth-and-nail fighting that people would like to think is only seen in wild beasts.
a listing for the some of the potential party members you'll meet at the start of the game. i've been writing off and on over the past few months, and this is what's come out. i'll post the four ladies tomorrow after i've had time to type them up; hopefully after that i'll be in the mood to pick coding back up. the women are:
Larich - Short Soldier
Caroline - The Amazon
Esther - Queen of War
Kelson - White Rose
Pascavis is a Imperial master swordsman, recently retired from the Doren guard. After years of hard work and climbing ranks, he began to feel a dissatisfaction with his work. His settled on the idea of becoming an adventurer, always having been intruiged by the strange wanderers that he met so often during his work, usually getting into some sort of trouble. All the same, he sees the Guild's training process as a necessity, because while he can hold his own against any of the combat trainers, his wilderness survival skills were almost nonexistent, having spent his entire life in the city. While constant association with the city's criminal element has hardly left him naieve, he is somewhat ignorant of life outside the city's well-ordered and civil culture.
As a friend, Pascavis is something of a big brother, taking a somewhat protective mentor role if they're weaker than him and a acting as a staunch ally and loyal friend if they're equally matched or stronger than him. As a romantic interest, Pascavis is somewhat awkward, his life in the city guard having left him with time for only a few short relationships. He tends to follow the player's lead, rather than take the initiative on his own. Pascavis has no romantic interest in other men.
Pascavis's story arc revolves around the disconnect he feels between his strength and his possession of it. He is a fantastic fighter, but has always lent his sword to the causes of others, and never his own, to the point where he isn't even sure if he has a purpose on his own.
Caspar - The Hero Born
Caspar is a Highborn from Knell, seeking to become a famous adventure - revered, respected, and feared. His life, to this point, has been spent working towards this goal; he has studied swordsmanship, law, etiquette, court politics, learned how to survive in the wilds, repair his armor and weapons, and anything else he could possibly imagine might be worthwhile to know when questing for fame and glory; everything, that is, except how to be a figure worth admiring. Caspar is incredibly competitive but somewhat good natured about it; in truth, he's too focused on himself to consider actually trying to sabotage anyone else.
Caspar sees the potential the player has if befriended, and quickly seeks to ensure his own greatness by associating himself with the player. The two train together and Caspar makes his loyalty known by deeds as well as words, but all the same, his drive to compete sets him up as a sort of rival. Caspar can (and will) fall in love with any player that happens to strike his fancy, male, female, or otherwise. As in everything else, he tends to be somewhat demanding and self-centered.
Caspar's arc explores the relationships between fame, strength, and social power. If such a book had been written in this world, Caspar would consider 'The Prince' to be his bible.
Rex - The Unfortunate Giant
Rex is a Lizardkin born abnormally large. He stands as tall as an Imperial, with a slim and powerfully muscled body that comes almost without effort. Such individuals are not entirely unheard of among the Lizardkin, but Rex lacks the thick armor-like scales that usually come with his size. The combination of size and a distinct, almost draconic, appearance generally means those like Rex are heralded as great leaders, but his utterly mundane scales leave him stranded somewhere in the middle. Unable to command the respect needed to lead but never quite fitting in among the common people, Rex left the Sun Coast to seek his fate as an adventurer.
Rex and the player can easily become friends simply if the player accepts Rex as he is. Rex, for his part, feels some sort of deep strength in the player, some ethereal quality that seems to make them a born leader. His curiosity about the player, bordering sometimes on being awestruck with them, seats him into the role of a younger sibling. As a romantic interest, Rex finds himself drawn to this same ethereal quality. He sees a certain sort of premeditation in the way the player moves and speaks that utterly enchants him.
Rex's story centers around how he chooses to deal with the situation of his unique birth. It explores ideas surrounding tradition, social expectation, and personal desires.
Joachim - The Killer
Joachim is a calm and controlled older man that, like most Foresters, prefers to remain quiet when not directly spoken to. What makes him unusual is his temper. Whether because of his (rumored) Orcish heritage, some kind of disorder, or an outright curse, Joachim has a propensity to fall into a blind, unthinking rage when he feels his life is at risk. Joachim has joined the adventurer's guild after several years living as a near hermit, having finally decided to try and find something - anything - that can help him learn to control himself.
Joachim, regardless of whatever kind of relationship he has with the player, remains somewhat distant from them. As a friend, Joachim seems to take some small comfort in the player's almost cavaleir willingness to spar with him, to the point where he questions if they even believe his rages are real. As a romantic interest, Joachim is somewhat more complex; he is a bit of a romantic and helpless to the urges of his heart, but his sense tries to keep him from getting too close to anyone, lest he lose control at a bad time.
Joachim's arc examines the unavoidable violence that combat always entails,and where the line is drawn between a civil fight and the sort of tooth-and-nail fighting that people would like to think is only seen in wild beasts.
a listing for the some of the potential party members you'll meet at the start of the game. i've been writing off and on over the past few months, and this is what's come out. i'll post the four ladies tomorrow after i've had time to type them up; hopefully after that i'll be in the mood to pick coding back up. the women are:
Larich - Short Soldier
Caroline - The Amazon
Esther - Queen of War
Kelson - White Rose
5/26/2013
on user interface
so, the main reason that i wasn't satisfied with the old interface was that contained a lot of wasted space and unneeded information.
to begin, my basic thought is that any information presented on a given screen should be actionable; it should in some way inform the decisions that the player is making, or else it serves no purpose. stats like strength and agility can have an impact, but they're both very much persistent statistics; they don't change enough to really warrant providing constant updates as to their status. health is relevant; it changes frequently and directly effects whether a player will decide to seek or avoid combat. name is relevant (in parties) to show who owns what health. day and time are (or will be) relevant, because time will at some point impact which events occur when exploring.
level doesn't impact decision making. experience only needs to be listed if there's some sort of system (that the player can impact in a meaningful way) that changes your stats on level up based on some equipped item or such, in which case you're just providing the player with busywork in order to feel like they're getting the most out of the game, which is bad.
secondly, i don't know why there was a second panel for the 10key. yes, it allows mouse controls rather than keyboard - but it doesn't need to be so large. there's already a panel for system output, so that can be used to inform the player of their options, and all you need is a small bar beneath or above that for buttons.
the new ui is going to have 4 distinct sections: character display (party status; name/health, name/health), game text ("you are in a place"), system text ("options: 1. explore 2. find 3. move") and the button bar. no more text input bar; that can be done by popping up a window, since entering your character's name is really the only time it will be used.
i did get a new keyboard last night. this one has three broken shift keys.
to begin, my basic thought is that any information presented on a given screen should be actionable; it should in some way inform the decisions that the player is making, or else it serves no purpose. stats like strength and agility can have an impact, but they're both very much persistent statistics; they don't change enough to really warrant providing constant updates as to their status. health is relevant; it changes frequently and directly effects whether a player will decide to seek or avoid combat. name is relevant (in parties) to show who owns what health. day and time are (or will be) relevant, because time will at some point impact which events occur when exploring.
level doesn't impact decision making. experience only needs to be listed if there's some sort of system (that the player can impact in a meaningful way) that changes your stats on level up based on some equipped item or such, in which case you're just providing the player with busywork in order to feel like they're getting the most out of the game, which is bad.
secondly, i don't know why there was a second panel for the 10key. yes, it allows mouse controls rather than keyboard - but it doesn't need to be so large. there's already a panel for system output, so that can be used to inform the player of their options, and all you need is a small bar beneath or above that for buttons.
the new ui is going to have 4 distinct sections: character display (party status; name/health, name/health), game text ("you are in a place"), system text ("options: 1. explore 2. find 3. move") and the button bar. no more text input bar; that can be done by popping up a window, since entering your character's name is really the only time it will be used.
i did get a new keyboard last night. this one has three broken shift keys.
5/25/2013
a return
the illness is over, the body has been buried, and life is returning to normal. apologies for saying nothing about the hiatus or it's cause, but i prefer to keep my private life private.
i'm going to be rewriting the game engine from scratch, in part because i'm not happy with all of the crap cluttering the screen in the last release (also, it was willed with bugs and fail). the game is going to turn out to be more of a text adventure rpg, rather than roguelike; perhaps i should use this as an opportunity to change the name from 'frogue' to something else. expect a post detailing my thoughts about the old ui, the new ui in the next few days, followed by some npc profiles and (hopefully) a basic release before too long.
while i'm at it, maybe i should get a keyboard that doesn't have two broken shift keys.
i'm going to be rewriting the game engine from scratch, in part because i'm not happy with all of the crap cluttering the screen in the last release (also, it was willed with bugs and fail). the game is going to turn out to be more of a text adventure rpg, rather than roguelike; perhaps i should use this as an opportunity to change the name from 'frogue' to something else. expect a post detailing my thoughts about the old ui, the new ui in the next few days, followed by some npc profiles and (hopefully) a basic release before too long.
while i'm at it, maybe i should get a keyboard that doesn't have two broken shift keys.
11/03/2012
on real life
it's about 4 am now. about to finish getting ready for work today (leaving in a half hour). if everything goes smoothly i'll be home around 5, and from there i'll probably go in for a shift at my new, second job. i've already worked probably 42-44 hours this week.
nothing got done this week. too consumed by work and trying to stay sane.
nothing got done this week. too consumed by work and trying to stay sane.
10/29/2012
on elves
i've never been terribly fond of how elves are depicted in fantasy stories. idealistic, nearly perfect, incredibly intelligent, talented, and long lived... and yet, somehow, always in decline. all of the persecution complex without any reason to actually be persecuted. but besides that, there's a few things that i just never quite got.
first, there's the forests. with the exception of maybe old nordic legends, the elves always live in forests. this isn't really so bad, except the one major feature that almost all elves share is their fantastic eyesight. these two just don't seem to fit together so well with me; in the sort of thick, overgrown forest that elves so often inhabit, you don't get to take advantage of that kind of eyesight. being able to see ten miles means nothing if the trees keep you from seeing more than a few hundred feet. why are these two features almost always found together, when the one cancels out the advantage of the other? why wouldn't they live somewhere their incredible sight actually helps them?
the second thing that bugs me is the 'peaceful guardians of nature' thing. granted there are a few precious (and notably better) examples of this, but for the most part, elves are depicted as being reluctant to go to war or fight, excessively defensive of the sanctity of their forests, et cetera. i've never liked this sort of view of nature, as some sort of ideal state. nature isn't strictly a thing of beauty; it's senseless death, terrible tragedy, and heartless self-serving survivalism. the young and the weak die, the strong take advantage of the weak, and only the luckiest, craftiest, strongest, savagest, and most desperate survive. i've always seen civilization as an opposite to nature strictly because it tries to change this: a place where the young and weak are protected, the strong protect the weak, and the drive for individual survival is replaced by a drive for communal survival. nature doesn't have, or need, guardians; nature simply exists. if the forests wither and die, that is how nature progresses. if species go extinct, that is how nature progresses. but, that's an entirely other topic of an entirely different gravity.
the third thing about elves that i don't like is their long lives. most fantasy and sci fi lores fall into the problem of not properly handling long-lived species. humans can see four generations for 90 or 100 years; if elves mature at around the same rate, that could be 20-40 generations. the alternatives are that they take a long time to reach adult size (a 60 year old child), have absolutely absurd gestation periods (2-5 years), bizarre reproductive physiology (only capable of breeding every hundred years), or some other disadvantage that would probably preclude their species from advancing past a few generations. even worse, without any of these things, they live long enough that any significant reproductive rate would quickly see them spread across a world in great swarms. now, i could see how this could make for a good source of ancient ruins (spread like wildfire, quickly occupy the entire world, wars break out as overpopulation sets in, war leads to massive rapid technological/magical development, eventually a weapon is developed that virtually wipes the world clean of the race)... but that creates an extinct civilization, not one that's in decline.
haven't had much spare time the past few days. had a tire glow flat (had to replace it), worked long shifts this weekend... and admittedly, played a fair bit of borderlands 2. the mechromancer really kicks ass.
first, there's the forests. with the exception of maybe old nordic legends, the elves always live in forests. this isn't really so bad, except the one major feature that almost all elves share is their fantastic eyesight. these two just don't seem to fit together so well with me; in the sort of thick, overgrown forest that elves so often inhabit, you don't get to take advantage of that kind of eyesight. being able to see ten miles means nothing if the trees keep you from seeing more than a few hundred feet. why are these two features almost always found together, when the one cancels out the advantage of the other? why wouldn't they live somewhere their incredible sight actually helps them?
the second thing that bugs me is the 'peaceful guardians of nature' thing. granted there are a few precious (and notably better) examples of this, but for the most part, elves are depicted as being reluctant to go to war or fight, excessively defensive of the sanctity of their forests, et cetera. i've never liked this sort of view of nature, as some sort of ideal state. nature isn't strictly a thing of beauty; it's senseless death, terrible tragedy, and heartless self-serving survivalism. the young and the weak die, the strong take advantage of the weak, and only the luckiest, craftiest, strongest, savagest, and most desperate survive. i've always seen civilization as an opposite to nature strictly because it tries to change this: a place where the young and weak are protected, the strong protect the weak, and the drive for individual survival is replaced by a drive for communal survival. nature doesn't have, or need, guardians; nature simply exists. if the forests wither and die, that is how nature progresses. if species go extinct, that is how nature progresses. but, that's an entirely other topic of an entirely different gravity.
the third thing about elves that i don't like is their long lives. most fantasy and sci fi lores fall into the problem of not properly handling long-lived species. humans can see four generations for 90 or 100 years; if elves mature at around the same rate, that could be 20-40 generations. the alternatives are that they take a long time to reach adult size (a 60 year old child), have absolutely absurd gestation periods (2-5 years), bizarre reproductive physiology (only capable of breeding every hundred years), or some other disadvantage that would probably preclude their species from advancing past a few generations. even worse, without any of these things, they live long enough that any significant reproductive rate would quickly see them spread across a world in great swarms. now, i could see how this could make for a good source of ancient ruins (spread like wildfire, quickly occupy the entire world, wars break out as overpopulation sets in, war leads to massive rapid technological/magical development, eventually a weapon is developed that virtually wipes the world clean of the race)... but that creates an extinct civilization, not one that's in decline.
haven't had much spare time the past few days. had a tire glow flat (had to replace it), worked long shifts this weekend... and admittedly, played a fair bit of borderlands 2. the mechromancer really kicks ass.
10/24/2012
on the value of commant prompts
the next release is probably going to be in the form of a console window (the crappy black and white box), capable mostly of generating a character and displaying it. this sounds disappointingly familiar.
still, the code is getting largely rewritten. the crapwindow is mostly going to be used for proving that the code works, from which point it can easily be incorporated into the main program. the base system for organs is in place now (reporting and setting values). before i can go further, i'll need to rewrite the character generation. after that i can put some sort of demo out (and possibly an editor-type program to 'write' the race files), followed quickly by a version that allows saving and loading.
still, the code is getting largely rewritten. the crapwindow is mostly going to be used for proving that the code works, from which point it can easily be incorporated into the main program. the base system for organs is in place now (reporting and setting values). before i can go further, i'll need to rewrite the character generation. after that i can put some sort of demo out (and possibly an editor-type program to 'write' the race files), followed quickly by a version that allows saving and loading.
10/21/2012
on misunderestimation
taking a bit longer than i thought it would. still need to spend some time coming up with the formula for how the game generates real length values from the relative values for the relevant organs (tails, hair, fur, tongue, penis, clit, nipples, and tentacles), while the others (wings, arm, ear, nose, and horn) can just stay a vague 'you have unusually long arms' and so on. unless there are people with a serious fetish for nose-fucking i don't see anyone complaining about that.
did run into a bit of frustration because i forgot that the organ functions are in a class outside of the entity class, so they don't have innate access to their host entity's height value, which is necessary for calculating the real values of relative stats. still, that just means i need a function that takes a relative value, height value, and organ type to spit out the proper number. might be handy for reporting information for npcs, i suppose.
did run into a bit of frustration because i forgot that the organ functions are in a class outside of the entity class, so they don't have innate access to their host entity's height value, which is necessary for calculating the real values of relative stats. still, that just means i need a function that takes a relative value, height value, and organ type to spit out the proper number. might be handy for reporting information for npcs, i suppose.
10/18/2012
on dicks
i don't like tracking the actual size of organs. when you're dealing with a number of races whose size relative to one another can differ so greatly (goblins range from 3'6" to 5'9", while imperials are a minimum of 6' and as tall as 10'6"), it gets very difficult to tell what exactly constitutes an 'average' size. 8" isn't bad for a standard six foot human, but for that short-as-hell goblin it's virtually knee-length, and for the tall-as-hell imperial it's just embarrassing. fortunately there's an answer for this, one that's (sort of) already in the game.
the game doesn't actually track your weight in terms of pounds, or kilograms. instead, it tracks your body mass index (or some approximation of it), and then multiplies that against your height (i think the formula is height^2 * BMI / 28,800, with height being measured in 1/10th inches and weight coming out in pounds - no idea how accurate this is; if someone has an actual formula i'd be happy to see it). i'm thinking of just doing something similar and then applying it to things like hair, genitals, wings, etc, to make it much easier to tell what is large and what isn't. this is mostly for the player's benefit - without graphics, it's sometimes easy to forget that you're actually four feet tall, and that (otherwise) unimpressive tool is actually quite large for your size.
it will also help prevent people from walking around with dongs that drag on the ground, but that's just a side benefit.
finished a large deal of the organ handling methods tonight. this is part of the reason i wanted to redo them in the fashion i did; instead of having 3 separate methods for virtually every piece of data stored by each organ (get, set, modify), it's all been condensed to about 40. now, the syntax is: getOrganType(1, head) or getOrganType(head). technically it's actually about 160 methods, but half of them are essentially 'halves' of the same function (one handling basic organs and the other handling sexual organs; the two store slightly different information and thus need different data structures, and thereby methods) and of those, half are one line methods that manually call getOrganType(1, head) when you just put in getOrganType(head). and yes, i could drop this number by half by only using a single data type for all organs and then just ignoring the extra sexy-type information for things like legs and arms, but the only extra code that gets written is a copy/pasted header with the names of the data types being changed. the rest of the code would need to get written either way.
i have tomorrow off, so should be done with organs by the end of then. probably going to spend several hours streaming (if anyone actually watches).
the game doesn't actually track your weight in terms of pounds, or kilograms. instead, it tracks your body mass index (or some approximation of it), and then multiplies that against your height (i think the formula is height^2 * BMI / 28,800, with height being measured in 1/10th inches and weight coming out in pounds - no idea how accurate this is; if someone has an actual formula i'd be happy to see it). i'm thinking of just doing something similar and then applying it to things like hair, genitals, wings, etc, to make it much easier to tell what is large and what isn't. this is mostly for the player's benefit - without graphics, it's sometimes easy to forget that you're actually four feet tall, and that (otherwise) unimpressive tool is actually quite large for your size.
it will also help prevent people from walking around with dongs that drag on the ground, but that's just a side benefit.
finished a large deal of the organ handling methods tonight. this is part of the reason i wanted to redo them in the fashion i did; instead of having 3 separate methods for virtually every piece of data stored by each organ (get, set, modify), it's all been condensed to about 40. now, the syntax is: getOrganType(1, head) or getOrganType(head). technically it's actually about 160 methods, but half of them are essentially 'halves' of the same function (one handling basic organs and the other handling sexual organs; the two store slightly different information and thus need different data structures, and thereby methods) and of those, half are one line methods that manually call getOrganType(1, head) when you just put in getOrganType(head). and yes, i could drop this number by half by only using a single data type for all organs and then just ignoring the extra sexy-type information for things like legs and arms, but the only extra code that gets written is a copy/pasted header with the names of the data types being changed. the rest of the code would need to get written either way.
i have tomorrow off, so should be done with organs by the end of then. probably going to spend several hours streaming (if anyone actually watches).
10/16/2012
on skinless wolves
you land the first and final blow, killing the wolf after a short scuffle. they aren't much of a challenge anymore; you're probably one of the greatest swordsmen on the continent. the beast dispatched, you pull out your trusty knife, preparing to skin the animal. oops; you put a large gash in it's hide. no problem, it's still salvageable. oops. there goes another bit; still, you can make two small hides. or three; oops. make that four. before long, the hide is completely unusable. you went from a green adventurer to master swordsmen in less than a year, but still can't skin an animal without mangling the hide.
it's a trope so common that calling attention to it has almost become a trope in and of itself: you get sent off to collect ten wolf pelts, or a dozen goat hooves, or twenty bear asses, and seem to encounter nothing but skinless wolves, legless goats, and assless bears. to mention nothing of the fact that by your second week, you've decimated the local wolf, goat, and bear populations. unlike the one i posted yesterday, this has a very simple practical solution (infinite wolves), but making it thematically sensible is the hard part.
i've already sort of gone over this, but i don't like the idea of the brave hero of the land wantonly raping and murdering half of everyone they meet. or at least, not seeing any consequence for it. so, i decided that the combat system was an abstract one; rather than actually connecting with every attack, health represents an abstract of the character's stamina, combat ability, luck, and training. it's why it goes up with your level, when you don't actually grow extra flesh or redundant vital organs. the fight doesn't end when one person falls dead; it ends when they reach the point of exhaustion, realize they can't win, and surrender. the same concept can be applied to wild animals - sooner or later that wolf will realize that it's outmatched, turn tail and bolt. obviously killing wildlife is more acceptable (and arguably necessary for a healthy ecosystem; preventing overpopulation of predator of prey species) than killing people.
so, you'll still get your wolf pelts, and you'll even get them from every wolf you kill - you just won't necessarily kill every wolf that you encounter. of course there are still a few (minor) issues; if you get jumped by a bandit and they surrender, do you tie them up and let them get devoured by all the wolves you've pissed off?
going to be streaming until about 11 tonight. more coding, more work on organs.
http://www.livestream.com/uldegoagogo
done a bit early. programming lists make me want to tear my hair out. assuming that what i have is working (which i think it should), tomorrow i just need to go through and finish all of the reporting functions (that return things like organ length, type, color, etc). it's not terribly difficult busy work, but it still needs to get typed.
it's a trope so common that calling attention to it has almost become a trope in and of itself: you get sent off to collect ten wolf pelts, or a dozen goat hooves, or twenty bear asses, and seem to encounter nothing but skinless wolves, legless goats, and assless bears. to mention nothing of the fact that by your second week, you've decimated the local wolf, goat, and bear populations. unlike the one i posted yesterday, this has a very simple practical solution (infinite wolves), but making it thematically sensible is the hard part.
i've already sort of gone over this, but i don't like the idea of the brave hero of the land wantonly raping and murdering half of everyone they meet. or at least, not seeing any consequence for it. so, i decided that the combat system was an abstract one; rather than actually connecting with every attack, health represents an abstract of the character's stamina, combat ability, luck, and training. it's why it goes up with your level, when you don't actually grow extra flesh or redundant vital organs. the fight doesn't end when one person falls dead; it ends when they reach the point of exhaustion, realize they can't win, and surrender. the same concept can be applied to wild animals - sooner or later that wolf will realize that it's outmatched, turn tail and bolt. obviously killing wildlife is more acceptable (and arguably necessary for a healthy ecosystem; preventing overpopulation of predator of prey species) than killing people.
so, you'll still get your wolf pelts, and you'll even get them from every wolf you kill - you just won't necessarily kill every wolf that you encounter. of course there are still a few (minor) issues; if you get jumped by a bandit and they surrender, do you tie them up and let them get devoured by all the wolves you've pissed off?
going to be streaming until about 11 tonight. more coding, more work on organs.
done a bit early. programming lists make me want to tear my hair out. assuming that what i have is working (which i think it should), tomorrow i just need to go through and finish all of the reporting functions (that return things like organ length, type, color, etc). it's not terribly difficult busy work, but it still needs to get typed.
on races
say you're an orc. or, you were an orc. you've gone off the straight and narrow (so to speak), given up a bit of yourself to become a stronger adventurer, exposed yourself to strange magic in a dungeon, and drunk a few under-the-counter potions that you hope will help you impress your lady friends. between the dark red scales, viciously clawed hands, and serpentine tail you look more like a dragonkin now... but everyone still greets you as an orc. what?
this game is going to have lots of races. orcs, dwarves, humans, wolfmen, and more exotic creatures like the golems and slimes. race isn't exactly a single uniform slider that can be controlled by a single number. so how does it get identified? there's two basic solutions:
first, keep a 'bloodline' count for each racial archetype (human, orc, dragon, etc), and define it by what preset race you're closest to. so humans are 100% human, orcs are 100% orc, and orckin have at least 25% human and 50% orc (or 25% orc and 50% human). each time you get exposed to a type of mutative force, you gain or lose a chunk of the appropriate bloodline. when you reach certain levels of a given bloodline, certain changes either kick in or go away; for instance, 10% dragon might give you horns, 20% might be clawed hands, 30 would be scales and 40 would be a tail. if you go from 0 to 50, you gain horns, hands, scales, and tail. if you get mutated another way and go down to only 30% dragon, you lose the tail.
this has a few problems from a gameplay perspective: how do you piss around with the fractions? if you're 25% human, 25% orc, 25%dragon and 25% dwarf and drink a potion that adds 5% horse, where does that 5% come from? 1.25 from each of your existing? if you just assign each bloodline a static number (rather than a percentage) you can calculate percentage easily enough... but then you end up with things like a character that's 0.5% orc, 1.25% dwarf, 2.25% cat, 3% dog, etc, etc. although, this could easily end badly, with characters becoming increasingly difficult to change as time goes on; while this could be good thematically, if the player only has the ability to gain demon wings after defeating demons at higher levels in the game, even a powerful potion could only move their race a fraction of a percent, since they would have already drank countless potions to get there.
you could go into things like introducing bloodline decay (eg, if you have 5 points in orc blood and 100 points in human blood, every day the orc blood goes down by one until you're free of it's taint), but that would require a lot of tweaking to see how fast things should decay, avoiding making it too high to make it impossible for characters to get the transformation they want without making it too low to make the decay worthless. if a specific item or effect doesn't occur often enough, frustrated players can't get their dragon wings and quit. and what about the people who want dragon wings, but not scales?
or, the second solution: just apply transformations on either an absolute (use item x, transformation y always occurs) or random/semi-random (use item x, transformation w, y, or z all have a chance of happening) basis, and then 'audit' the players race. essentially, this would require programming a flow chart:
does the player have humanoid legs, or something else? (humanoid -> go to elfkin, humans, dwarves, imperials, plainsdwellers, etc) (else -> go to slimes, centaur, naga, etc) from humanoid, ask does it have fur? (yes -> go to roamers, foresters, imperials, trolls, etc) (no -> go to humans, goblins, etc) and keep narrowing things down until you've narrowed them down to a specific race. if they simply don't fit any of the categories (for instance: pointed ears, bright blue fur, reptillian claws, four tits and a giant throbbing tentacle cock), they either get classified as a 'mongrel' (for mundane differences; looking humanoid, but not quite being orc, elfkin, human, or etc), 'mutant' (for more bizarre mutations, as the one mentioned previously) or 'abomination' (for the guy that modifies their character to have a foot long dick growing out their forehead).
i think i prefer the second method - it would allow the player to custom pick their body modifications, it'd be overall easier to code, and i still wouldn't have a good answer for things like 99% dragon pc's or people that became 10% 10 races.
worked on organs some more tonight. in addition to all the old stuff, the game now tracks your mouth, tongue, 'lungs', 'stomach', and tentacles, as well as tattoos and piercings. the mouth thing should allow for features like fangs and tusks, tongue should allow for kinky blowjobs, lungs and stomach will be able to track things like ingested or breathed toxins (i figure, it could lead to some fun events like certain toxin-resistant races spiking their own drink with aphrodisiac, then handing it off to someone else). tattoos and piercings should be obvious, but as a side note, tattoos will also include natural patterning, like tiger stripes or other fur and scale patterns. 'tentacle' is another sexual organ class, like dicks. because all organs use the same basic format with variables identifying what body part they represent, they all share methods: lungs will have a 'get color' function, although it only applies to skin, hair, and the like. still, the actual coding should be smart enough not to try and call for the color of a lung-type organ, so this shouldn't be an issue, and the method itself can always check to make sure the call is relevant to the organ type and return a specific answer as an error message if it's not.
on a side note, the existing system makes it much easier to add (or remove) certain organs from certain entities, so for all of those out there who hate furries, there'll be a file to swap out that turns all of the mean, nasty horse-like imperials into safely human half-giants by removing the lines that tell the game to generate fur, hoofed feet, a tail, and so forth. it'll take a bit more work before races can actually be added via these files (there will need to be a way to tell the game how to identify that race, as an example), but eventually it should be possible.
this game is going to have lots of races. orcs, dwarves, humans, wolfmen, and more exotic creatures like the golems and slimes. race isn't exactly a single uniform slider that can be controlled by a single number. so how does it get identified? there's two basic solutions:
first, keep a 'bloodline' count for each racial archetype (human, orc, dragon, etc), and define it by what preset race you're closest to. so humans are 100% human, orcs are 100% orc, and orckin have at least 25% human and 50% orc (or 25% orc and 50% human). each time you get exposed to a type of mutative force, you gain or lose a chunk of the appropriate bloodline. when you reach certain levels of a given bloodline, certain changes either kick in or go away; for instance, 10% dragon might give you horns, 20% might be clawed hands, 30 would be scales and 40 would be a tail. if you go from 0 to 50, you gain horns, hands, scales, and tail. if you get mutated another way and go down to only 30% dragon, you lose the tail.
this has a few problems from a gameplay perspective: how do you piss around with the fractions? if you're 25% human, 25% orc, 25%dragon and 25% dwarf and drink a potion that adds 5% horse, where does that 5% come from? 1.25 from each of your existing? if you just assign each bloodline a static number (rather than a percentage) you can calculate percentage easily enough... but then you end up with things like a character that's 0.5% orc, 1.25% dwarf, 2.25% cat, 3% dog, etc, etc. although, this could easily end badly, with characters becoming increasingly difficult to change as time goes on; while this could be good thematically, if the player only has the ability to gain demon wings after defeating demons at higher levels in the game, even a powerful potion could only move their race a fraction of a percent, since they would have already drank countless potions to get there.
you could go into things like introducing bloodline decay (eg, if you have 5 points in orc blood and 100 points in human blood, every day the orc blood goes down by one until you're free of it's taint), but that would require a lot of tweaking to see how fast things should decay, avoiding making it too high to make it impossible for characters to get the transformation they want without making it too low to make the decay worthless. if a specific item or effect doesn't occur often enough, frustrated players can't get their dragon wings and quit. and what about the people who want dragon wings, but not scales?
or, the second solution: just apply transformations on either an absolute (use item x, transformation y always occurs) or random/semi-random (use item x, transformation w, y, or z all have a chance of happening) basis, and then 'audit' the players race. essentially, this would require programming a flow chart:
does the player have humanoid legs, or something else? (humanoid -> go to elfkin, humans, dwarves, imperials, plainsdwellers, etc) (else -> go to slimes, centaur, naga, etc) from humanoid, ask does it have fur? (yes -> go to roamers, foresters, imperials, trolls, etc) (no -> go to humans, goblins, etc) and keep narrowing things down until you've narrowed them down to a specific race. if they simply don't fit any of the categories (for instance: pointed ears, bright blue fur, reptillian claws, four tits and a giant throbbing tentacle cock), they either get classified as a 'mongrel' (for mundane differences; looking humanoid, but not quite being orc, elfkin, human, or etc), 'mutant' (for more bizarre mutations, as the one mentioned previously) or 'abomination' (for the guy that modifies their character to have a foot long dick growing out their forehead).
i think i prefer the second method - it would allow the player to custom pick their body modifications, it'd be overall easier to code, and i still wouldn't have a good answer for things like 99% dragon pc's or people that became 10% 10 races.
worked on organs some more tonight. in addition to all the old stuff, the game now tracks your mouth, tongue, 'lungs', 'stomach', and tentacles, as well as tattoos and piercings. the mouth thing should allow for features like fangs and tusks, tongue should allow for kinky blowjobs, lungs and stomach will be able to track things like ingested or breathed toxins (i figure, it could lead to some fun events like certain toxin-resistant races spiking their own drink with aphrodisiac, then handing it off to someone else). tattoos and piercings should be obvious, but as a side note, tattoos will also include natural patterning, like tiger stripes or other fur and scale patterns. 'tentacle' is another sexual organ class, like dicks. because all organs use the same basic format with variables identifying what body part they represent, they all share methods: lungs will have a 'get color' function, although it only applies to skin, hair, and the like. still, the actual coding should be smart enough not to try and call for the color of a lung-type organ, so this shouldn't be an issue, and the method itself can always check to make sure the call is relevant to the organ type and return a specific answer as an error message if it's not.
on a side note, the existing system makes it much easier to add (or remove) certain organs from certain entities, so for all of those out there who hate furries, there'll be a file to swap out that turns all of the mean, nasty horse-like imperials into safely human half-giants by removing the lines that tell the game to generate fur, hoofed feet, a tail, and so forth. it'll take a bit more work before races can actually be added via these files (there will need to be a way to tell the game how to identify that race, as an example), but eventually it should be possible.
10/14/2012
well, shit
started work at 5.30 am today. going to get home tonight at about 9.30 pm, if i'm lucky. not terribly happy about that.
i was planning on doing something tonight, but i guess not.
i was planning on doing something tonight, but i guess not.
10/13/2012
brainstorming
one part of the changes to how body types are stored is that all color information now uses the same table to reference what color is being depicted; so, instead of '1' meaning blue for eyes and black for hair, it's now always albino (which is what it was for skin. not all descriptors make sense for all organs, but that's fine.)
as a part of compiling a complete list (or complete enough) of what can look like what, i felt that i should post what i did have, and give people the ability to look it over to see of their favorite skin or eye color missed. this is a direct copy/paste from whats in the code, so it's gonna look a bit wonky instead of being neatly arranged into two columns.
//universal color chart
// 0 = translucent 1 = albino
// 2 = chalk 3 = cream
// 4 = pale 5 = pink
// 6 = peach 7 = pale yellow
// 8 = tan 9 = mulatto
//10 = burnt 11 = olive
//12 = ruddy 13 = chocolate
//14 = deep brown 15 = brown
//16 = light brown 17 = pearl
//18 = opal 19 = bronze
//20 = copper 21 = black
//22 = pitch 23 = charcoal
//24 = blackened blue 25 = deep gray
//26 = gray 27 = soft gray
//28 = pepper 29 = pine green
//30 = brackish green 31 = green
//32 = pale green 33 = orange
//34 = pale orange 35 = dark orange
//41 = pale yellow 42 = bright yellow
//43 = sand yellow 44 = blue
//45 = pale blue 46 = neon blue
//47 = navy blue 48 = red
//49 = pale red 50 = deep red
//51 = jet black 52 = blonde
//53 = platinum blonde 53 = sandy blonde
//54 = golden blonde 55 = strawberry blonde
//56 = dirty blonde 57 = ash blonde
//58 = deepest brunette 59 = chestnut brown
//60 = golden brown 61 = ash brown
//62 = burnt orange 63 = auburn
//64 = brick red 65 = fair red
//66 = fair orange 67 = pale gray
//68 = pine green 69 = moss green
//70 = onion white 71 = gold
//72 = brass 73 = deep gold
//74 = faint gold 75 = silver
//76 = platinum 77 = white gold
//78 = pink 79 = purple
//80 = amber 81 = hazel
//82 = violet 83 = sapphire
//84 = emerald 85 = topaz
//86 = diamond 87 = granite
//88 = marble 89 = sandstone
the last three are for use with golem-type character skin. remember that this list should cover eyes, hair, fur, and skin, as well as tattoos, clothing, and natural pattern markings (like tiger stripes or the like). got something i missed? post text, a picture, or a color sample. probably going to put a post like this up on /tg/.
as a part of compiling a complete list (or complete enough) of what can look like what, i felt that i should post what i did have, and give people the ability to look it over to see of their favorite skin or eye color missed. this is a direct copy/paste from whats in the code, so it's gonna look a bit wonky instead of being neatly arranged into two columns.
//universal color chart
// 0 = translucent 1 = albino
// 2 = chalk 3 = cream
// 4 = pale 5 = pink
// 6 = peach 7 = pale yellow
// 8 = tan 9 = mulatto
//10 = burnt 11 = olive
//12 = ruddy 13 = chocolate
//14 = deep brown 15 = brown
//16 = light brown 17 = pearl
//18 = opal 19 = bronze
//20 = copper 21 = black
//22 = pitch 23 = charcoal
//24 = blackened blue 25 = deep gray
//26 = gray 27 = soft gray
//28 = pepper 29 = pine green
//30 = brackish green 31 = green
//32 = pale green 33 = orange
//34 = pale orange 35 = dark orange
//41 = pale yellow 42 = bright yellow
//43 = sand yellow 44 = blue
//45 = pale blue 46 = neon blue
//47 = navy blue 48 = red
//49 = pale red 50 = deep red
//51 = jet black 52 = blonde
//53 = platinum blonde 53 = sandy blonde
//54 = golden blonde 55 = strawberry blonde
//56 = dirty blonde 57 = ash blonde
//58 = deepest brunette 59 = chestnut brown
//60 = golden brown 61 = ash brown
//62 = burnt orange 63 = auburn
//64 = brick red 65 = fair red
//66 = fair orange 67 = pale gray
//68 = pine green 69 = moss green
//70 = onion white 71 = gold
//72 = brass 73 = deep gold
//74 = faint gold 75 = silver
//76 = platinum 77 = white gold
//78 = pink 79 = purple
//80 = amber 81 = hazel
//82 = violet 83 = sapphire
//84 = emerald 85 = topaz
//86 = diamond 87 = granite
//88 = marble 89 = sandstone
the last three are for use with golem-type character skin. remember that this list should cover eyes, hair, fur, and skin, as well as tattoos, clothing, and natural pattern markings (like tiger stripes or the like). got something i missed? post text, a picture, or a color sample. probably going to put a post like this up on /tg/.
10/12/2012
(samuel clemens reference)
so, what happened?
in short, a family member became very ill and i had to spend some time taking care of them. between this and work i had little free time for anything, much less something that takes as much mental energy as writing code. which is just as well, since (upon returning to the project) the code was a fair mess. i'm going to be simplifying how the program handles it's base behavior (from about 15 different ways, with different behaviors for things like saving, loading, etc) to three (combat, input, and output). most of the old event text is still usable, though, so that shouldn't be too bad.
also overhauling how characters are stored. i don't like having a the 150-odd disparate integers saved as hard and fast data points. hard coded character limits are bad, m'kay, something that i noticed later on when i felt the need to go back and add things like facial hair, pregnancy, and lactation support. so, everything is going to be handled for a (relatively) simple system of objects; the 'entity' (a character) now has 'organs' (things like limbs), meaning that the list can be expanded or contracted easily. this means that, instead of having to code eight extra sets of penis data for the people that want nine dongs, you just need to add a penis-type organ however many times. there's a method for handling text output as far as what organ shows up where; i don't think i'm going to bother trying to make locations exclusive (so if you want fifteen cocks growing out of your forehead, go ahead).
naturally, though... this entails a significant rewrite of how characters report, change, and save their physical data. all the same, for those interested,
http://www.livestream.com/uldegoagogo
(streamed noon till 2; probably more later)
8 pm: streaming again (ended at 9:30)
(and for those wondering, yes, they got better)
in short, a family member became very ill and i had to spend some time taking care of them. between this and work i had little free time for anything, much less something that takes as much mental energy as writing code. which is just as well, since (upon returning to the project) the code was a fair mess. i'm going to be simplifying how the program handles it's base behavior (from about 15 different ways, with different behaviors for things like saving, loading, etc) to three (combat, input, and output). most of the old event text is still usable, though, so that shouldn't be too bad.
also overhauling how characters are stored. i don't like having a the 150-odd disparate integers saved as hard and fast data points. hard coded character limits are bad, m'kay, something that i noticed later on when i felt the need to go back and add things like facial hair, pregnancy, and lactation support. so, everything is going to be handled for a (relatively) simple system of objects; the 'entity' (a character) now has 'organs' (things like limbs), meaning that the list can be expanded or contracted easily. this means that, instead of having to code eight extra sets of penis data for the people that want nine dongs, you just need to add a penis-type organ however many times. there's a method for handling text output as far as what organ shows up where; i don't think i'm going to bother trying to make locations exclusive (so if you want fifteen cocks growing out of your forehead, go ahead).
naturally, though... this entails a significant rewrite of how characters report, change, and save their physical data. all the same, for those interested,
http://www.livestream.com/uldegoagogo
(streamed noon till 2; probably more later)
8 pm: streaming again (ended at 9:30)
(and for those wondering, yes, they got better)
5/05/2012
not dead
apparently, i'm most productive after locking myself in a closet with a laptop. the upside of that is that i've at least figured out how to get myself focused - although, getting out of the closet afterward is presenting a bit of a problem.
conversation with the elf is done. still need to think of a few threads to add for methods of recruiting you to your party (for when that gets put in) and romancing her (which will occur once the game is feature-complete), but there should be some good material in the setup - particularly if you look up david wild32's guide to editing saves on the 'something is rotten' blog post and max your charm and looks.
conversation with the elf is done. still need to think of a few threads to add for methods of recruiting you to your party (for when that gets put in) and romancing her (which will occur once the game is feature-complete), but there should be some good material in the setup - particularly if you look up david wild32's guide to editing saves on the 'something is rotten' blog post and max your charm and looks.
4/22/2012
slow progress
things going slow. ended up working six days this week and adding several dozen extra functions that are handy now, and will be necessary later down the line, mostly dealing with things like describing whatever it is that's coming out of your various orifices. probably going to need to do more down the line (for things like skin), but for now, it's fine the way it is.
admittedly, picking sword of the stars back up didn't give me any extra time to program. i need to start working on a laptop with nothing but a compiler installed on it, or something.
admittedly, picking sword of the stars back up didn't give me any extra time to program. i need to start working on a laptop with nothing but a compiler installed on it, or something.
4/15/2012
something is rotten in the state of denmark
i promised to make a release tonight, but it's simply not ready. the elf's initial encounters are all finished (all the greets and all of the text for peeping on her), but i didn't have time to finish her primary dialogue. still haven't tested combat either.
a big thanks to David Wild32 for helping me identify a bug that was causing your will to display improperly (and further kudos for messing around with the save system enough to actually find it).
a big thanks to David Wild32 for helping me identify a bug that was causing your will to display improperly (and further kudos for messing around with the save system enough to actually find it).
4/14/2012
release coming sunday
although in retrospect, the best stuff can't be accessed without swapping around your character's stats by editing the save files... which by some reports, don't work.
regardless there will be some kind of release, probably a quick guide on how to futz with the save files to let people (a) cheat and (b) actually see the content. there's one event in particular that only occurs when you peep on her with a cute guy, and only if you haven't introduced yourself yet. i think, later on, i might include a bit where you can ask to roleplay with her (once you've established a relationship) so i can reuse the text.
anyway, the peeping scenes are around half done now. i have the rest 'sketched' out, so i know what's going to happen and just need to put them to words. with a bit of luck, i'll get them done early or get off work early today (or both), and have some time to bug test the combat system more than once.
regardless there will be some kind of release, probably a quick guide on how to futz with the save files to let people (a) cheat and (b) actually see the content. there's one event in particular that only occurs when you peep on her with a cute guy, and only if you haven't introduced yourself yet. i think, later on, i might include a bit where you can ask to roleplay with her (once you've established a relationship) so i can reuse the text.
anyway, the peeping scenes are around half done now. i have the rest 'sketched' out, so i know what's going to happen and just need to put them to words. with a bit of luck, i'll get them done early or get off work early today (or both), and have some time to bug test the combat system more than once.
4/13/2012
Codex: Wine Jellies
Average height: 3 inches (~7 cm)
Average weight: 1 lb (~.5 kg)
Wine jellies are a small, tough, and opaque breed of feral slime endemic to the continent. They generally have a grayish color to them, sometimes darkening to near black if their diet includes lots of protein, and both their behavior and intelligence are comparable to rats. They have very weak digestive fluid, and are unable to process meat until it has partly rotted. They act as scavengers, cleaning up bits of food and biological debris, occasionally causing trouble by knocking things over. They are placid enough to be kept as pets, although unless their diet is carefully controlled, they can reproduce quickly and become a major pest.
Wine jellies take their name from an old brewing practice, generally accepted to have been invented by a Highborn, of immersing mature jellies in a tub of grape juice mixed with a bit of yeast. The jellies will instinctively absorb large amounts of the sugar-rich liquid, far more than they can actually digest, and swell to much larger than normal sizes. In this state their stretched outer membrane become slightly transparent and the jelly becomes virtually immobile. They are left in this state for several months as the grape juice ferments into wine inside of them. While this has the somewhat comical side effect of leaving them intoxicated for a period of several months, it also produces a 'pure' flavor of wine, lacking the additional tastes that come from fermenting inside wooden barrels. The wine is harvested simply by puncturing the jelly (which is relatively unharmed by the entire process).
Wine jellies are technically edible once cooked, tasting just slightly sweet, but are mostly just gooey. They are commonly used as thickener in soups or sauces, filler in some animal feed, or as fishing bait.
Average weight: 1 lb (~.5 kg)
Wine jellies are a small, tough, and opaque breed of feral slime endemic to the continent. They generally have a grayish color to them, sometimes darkening to near black if their diet includes lots of protein, and both their behavior and intelligence are comparable to rats. They have very weak digestive fluid, and are unable to process meat until it has partly rotted. They act as scavengers, cleaning up bits of food and biological debris, occasionally causing trouble by knocking things over. They are placid enough to be kept as pets, although unless their diet is carefully controlled, they can reproduce quickly and become a major pest.
Wine jellies take their name from an old brewing practice, generally accepted to have been invented by a Highborn, of immersing mature jellies in a tub of grape juice mixed with a bit of yeast. The jellies will instinctively absorb large amounts of the sugar-rich liquid, far more than they can actually digest, and swell to much larger than normal sizes. In this state their stretched outer membrane become slightly transparent and the jelly becomes virtually immobile. They are left in this state for several months as the grape juice ferments into wine inside of them. While this has the somewhat comical side effect of leaving them intoxicated for a period of several months, it also produces a 'pure' flavor of wine, lacking the additional tastes that come from fermenting inside wooden barrels. The wine is harvested simply by puncturing the jelly (which is relatively unharmed by the entire process).
Wine jellies are technically edible once cooked, tasting just slightly sweet, but are mostly just gooey. They are commonly used as thickener in soups or sauces, filler in some animal feed, or as fishing bait.
Subscribe to:
Posts (Atom)