- Sep 3, 2018
- 2,628
- 11,152
Well it took me some time as wellSo true - if just more people would understand it like you do!
Well it would be possible to bring hardcore stuff in early, but that would or should end into a "Game over" and I hate game over. And as I want to focus on consent, I obviously need to restrict the early game fetishes. Especially when I want one of the characters to be totally unexperienced.Nailed it.
Whatever engine is going to be chosen for this game - it will require simple definitions that can be translated into code.
Which is why i gave the pseudocode example further down. Pseudocode is basically just a simplification of all you wrote earlier and cooked down to the actual necessary facts (attributes or fetishes). As it is supposed to be coded one day you will need some definition of limits - yes. An engine cant decide for you. You have to define each and every fetish and the conditions necessary to obtain/fulfil them. From what you wrote you want the player to decide - but you still have to define the playing field and the rules that apply. So limitations are actually good and necessary. One cant use the hardest spanking tool wqhen they are just starting out with spanking, spanking probably comes earlier than other fettishes etc etc. Everything is bound to have some kind of condition to be fulfilled before one can make the choice. Or the choice itself gets limited in duration or how heavy the actual performance can be. All this needs some rough translation into simple attributes and simple conditions - best written into pseudocode which is not tied to any particular engine. But pseudocode is easily understandable for a coder - and its those you lack right now to help you. These definitions make up the 'framework' of your story because they will lead to actual code and functions to perform whatever has to be executed in real code later.
At the moment I am experimenting a bit around with pseudocode and a flowchart. As I am a visual guy I need some kind of sumery/ schema.
Yeah something like: First BDSM-Play-Session - X specific fetishes are unlocked to use. Player can decide out of Y different fetishes with which to start. Session 1 has for example two scenes. Then I could make some kind of fetish categories. Like "Spanking"- category, which starts of with the hand. After using the hand an amount of times, you unlock the next level in this category, for example the paddle.You have to set the rules. Let me use a sport example to make clear why: In football (or soccer for our american friends here) you have a playing field and a given set of rules. But the players decide how to shoot and play the ball - there is no outside control about that. Your game has to work the same way. You deliver the contents of the playing field (fetishes and the connected rules and limitations/conditions for each of them but the players can choose how and if they want to use any or all of the available stuff.
That would be an example, but as I don't like grinding games, I want to make the scenes different even by using always the hand. So yeah that's something I have to think about.
I guess I kind of summarized it above :coldsweat:No you wouldnt. If you dont limit the choices or create rules you will end up in total chaos and thus your game becomes unplayable. Imagine a new player being able to basically torture the shit out of your new submissive right from the start - sounds wrong, correct? You could have it end in a game over of course - which would just lead to the player feeling miserable and cheated because you gave him the freedom to begin with. Users always ask for freedom but that is seldom 'total freedom'. Often they actually mean 'variety' and 'choices' when they talk about freedom. We as humans tend to require rule sets. We like to bend those rules or try to avoid them at times but we are naturally trying to find an order in something. Games without rules usually dont work and rules always mean limitation in some way.
Yeah somehow there has to be an interface between them :biggrin:It is and should be used more often. It is a great tool of communication between the hardcore geeks and writers or non-coders.