Development 0.3 - #3
Added 2024-08-11 21:44:41 +0000 UTCHello friends!
I've been trying my best to get creative over the past two weeks, but progress has been a bit slower than I'd like. I've managed to write 3 out of the planned 12 scenes for part 1. Knowing myself, I might tweak a few sentences here and there when I start working on the actual renders, but that's a task for future Pandy.
Anyway, I have two weeks of vacation coming up, and I plan to get stuff done. So, you can expect some good progress on the next status report. I'm really looking forward to it.
That's all for now, quick and to the point.
Enjoy your upcoming week!
Comments
illusion of choice through some decision boxes that move things around :D
Cyber
2024-08-14 19:54:06 +0000 UTCA DnD campaign is a dialogue though :D an AVN is mostly a monologue and therefore this isn't applicable unfortunately, would be cool if it was, though.
DebatingPanda
2024-08-14 19:42:24 +0000 UTCoh, i see what you did there with that first line lol. ps: one thing i learned from doign some DnD campaigns is that sometimes you can provide a story beat and then the your players will go completely off-the-beat and do their own shtick. And instead of feeling bad that your story beat didn't make it, just relabel it, restyle it, or save it for later, and then bring it back again later as if you were always going to do it there :P #BigBrain. Encapsulation at its finest lol.
Cyber
2024-08-13 18:50:25 +0000 UTCwhile that may be true........... got stuck as well, damn :D Yeah, choosing between approach A or B is the real pain. I'll just go with what I like the most, that worked out pretty well. I actually want to have more polls to have people more involved in the development process. Stay tuned for them! Those polls are weight based on the the supporters tier like the monthly wallpapers! :)
DebatingPanda
2024-08-13 08:49:26 +0000 UTCWait that's my bad. I got you stuck in an infinite loop lol. Damn semi columns. you were supposed to breathe after hitting the climax (narratively) lol. And yeah, the decision of "this or that" is like 90% of my pain at work... Try having to do that for decisions that will be locked in for 10 years and never fixed again π. Usually I end up separating those decisions into their own document or "investigation" and even drop a poll with colleagues (or patreons) for the truly annoying dilemmas. It could also be tier limited to inquire about something via polls and people will opt in willingly at a higher tier to help answer questions without getting spoiled accidentally. (+ You can turn that tier rating to a bonus discord channel and help fund your projects! "Gamify the pain.")
Cyber
2024-08-12 11:08:34 +0000 UTCThank you! I'm good for now, though. I just took 1 1/2 month break after 0.2 so now I'm eager to continue the story!
DebatingPanda
2024-08-12 09:27:36 +0000 UTC"Take ONE long deep breath and FUCKIN HOLD IT" - Instruction unclear, woke up in the hospital with a girl named Lucy worrying about me. /jk That's solid advice, I'm definitely going to test it out, thanks! :D I usually start with a list of breadcrumbs and then write it out when I reach that specific scene. But as you mentioned, the "OR this" - "OR this" options are where I get stuck sometimes. I often ask myself which path would be more entertaining to read and end up questioning both. Total Concentration Breathing activated! I really enjoyed that anime. Thanks again for the input, I'm heading back to work now! :)
DebatingPanda
2024-08-12 09:26:46 +0000 UTCI find solace in the fact that you call yourself future Pandy lol. I call Past Cyber because he either did something right or something wrong for Current Cyber...who's trying to either trying to reduce work\stress for or punt work\stress for Future Cybie. Current Cyber will become Past Cyber and the cycle repeats itself π. I guess that's a standard across all software engineers and programmers π #GitBlameYourself (Keep up the good work. I know from experience that the writing narratives and documents for a game or design is some of the worst creative mental blocks for us, even as a senior software engineer with ADHD and ocd\perfectionism. One advice I recommend to try to get yourself creative without falling into decision paralysis or churning, it's a little exercise I do for myself on the bad days: take a notepad (digital or paper, or whiteboard whichever is faster), And then think about one of the scenes that you want to do. Take ONE long deep breath and FUCKIN HOLD IT. You now have to write every single random thought that comes to you about that scene to describe it from start to finish without letting go of that breath. Your goal is to start at the starting point of the scene or document (my intro\purpose) and then get the last wireframe scene of the document (conclusion \recommendation). If you find that you ran out of breath before you reached the end of the document even with minimal bullet points or even scribble words? , that means you're churning and spending too much time focusing on the wrong detail somewhere along that document, and that spot that's churning you will get you demotivated or slowed down productivity if you were writing it top to bottom clearly. OR your scene itself should be broken into two parts with their own input\output (think of it like breaking down a nested batch of code and then extracting that long code into a separate function or class to keep it easier to read and review and reduce bugs) So then you take another breath and your goal is fix that mistake you made and rush to the end fo the scene with your goal of the scenes. Figure out your input and output of that scene and don't focus on the middle anymore. The middle of scenes or documents or code functions can always be changed as long as the expected inputs and outputs are met (encapsulated handshake design for plug and play). So now that you got yourself a chicken doodle ugly list of breadcrumbs that you scribbled fast from start to finish, take another deep breath and then try to take all your random words that you made and connect them together to form a sentence. It doesn't have to be coherent or perfect English. It's simply to help weed out the useless details that slow you down and get to the core\gist of what is ACTUALLY important. For example, if your first attempt (the beginning) you say "I want MC to grab ice cream. And your second attempt (the ending) says that the MC wakes up in bed not feeling well, you can now start to fill in the blanks by connecting the dots. It can be : MC went to get ice cream, ate too much ice cream, got stomach pain and went home and woke up unwell Or it could also be : MC went to get ice cream but along the way someone hit him with a baseball bat and stole his wallet and now he's in bed thinking about that moment unwell. Or it could be: MC went to get ice cream and thought about one of his friends that always loved that flavor of ice cream...mc hasn't seen that person in a while and when he goes to sleep he has a dream about them and can't remember their name so he wakes up feeling sad and unwell for some reason. OR it could also be something that you have as just flavor filler for later : MC goes to ice cream, something happens, doesn't matter, some placeholder event, need to mention new gang boss in town for later, fill this later, and something about morning stress or pain so that MC's friend checks on him And then just keep rinse and repeat it and suddenly you'll find out that you don't need motivation to write a full scene, because motivation is the biggest crippling failure in productivity. You don't need motivation, you just need better lungs and constant total concentration breathing (for all you demon slayer fans out there). And just like that you can get more work done without feeling motivated about it...the motivation shouldnt be the reason you start something, motivation should be the reason why you want to grow it or drive it home and finish it properly. Routine is what should be eh catalyst of creativity and the first step in getting momentum, not motivation, that comes later π. Anyway, sorry about the Ted talk, I'm a senior software engineer and I trained a lot of engineers under my belt that had similar productivity flags and I figured I'd share my 2 cents! Thanks for the game!
Cyber
2024-08-11 23:03:53 +0000 UTCbe sure to take a break when you can. you don't want burn out. if it takes a bit longer than you'd like, that's ok.
Bladeturbo
2024-08-11 22:51:54 +0000 UTC
