Godot Gamedev Diaries

https://parallelpapel.itch.io/bravesirknight/devlog/764274/release-5-is-out-stage-redesigns-no-new-adult-content

Some much needed level redesign was done for R5. I was initially torn between releasing it or holding it back until I could add more adult content. In the end, I opted to release it, as getting feedback on the level design would be useful.

My to-do list right now:
* New shield enemy, that is invincible from the front - possibly bear or cow
* New ranged enemy that throws a chakram or something that flies in a C curve - possibly feline
* Make a decent main menu screen
* Make proper graphics for the control scheme on the main menu
* Make better looking tilesets (note to self, tiles have to be 50x50 in size)
* Make better looking level backgrounds
* Find one new music to use for stage 3

Copying from my F95 post. Right now, imgbb isn't loading for me, nor is postimage.cc or even postimage.org, so no image uploads.
------------
So, having some trouble with my orc animation right now because of my own code working against me.

The problem: checking which sex scene to play happens both in the player AND the enemy's scripts. This is terrible because instead of having only one place to look at in order to fix, I have to keep checking two. How is this biting me in the ass? In the form of me not creating a "sex_on4s" for the orc gal. Since that part is written in the player script, I either work on a fix there, or create a proper "sex_on4s" animation for the orc, or create a dummy to stop some of the errors.

As if that wasn't enough, I also have to contend with this shit:


Yes, the face, hair and breasts are on the wrong side. Why? Because fuck if I know, Godot apparently hates working with bones. Keep in mind, this kind of error happens all the time with the orc gal in the editor, though a simple advance on any animation fixes everything's positions.


That's from the editor. Why in the fucking fuck that happens? Turns out it's because I'm being "lazy": the textures for the hair, chin, ear and face are all separate nodes, child nodes of the head shape. This means that, in theory, dealing with the parent node alone should replicate every position and rotation to its children.

This, however, becomes a problem because I'm not doing that straight on the textures, I'm doing that through a "RemoteTransform" node.
I'm not using these RemoteTransforms on the kobold enemy, but I'm using on the player and the princess, and the player's head textures can very easily "glitch" [URL='https://f95zone.to/threads/released-help-me-brave-sir-knight-a-godot-dev-diary-previously-just-sharing-my-great-idea.171385/post-11784188']if you move left-right fast[/URL], the head takes 1 extra frame to get in place with the rest of the body.
- Now that I actually know the fucking cause, I also understand why this is happening: Godot draws stuff on screen going from the bottom of each scene upwards. Child nodes are always drawn before the parent nodes. Due to the RemoteTransform, ONLY the parent node will be affected, a change that won't travel down until the next frame. Why, however, it's not properly updating while fucking the orc gal as shown way above, I still don't know.
- See, remote transforms were supposed to help in order to properly align the draw order of textures: you put the remote as a child of the bone, then just point to the actual texture, which will ideally be ordered elsewhere, so that it's easier to rearrange what piece goes on top of what, like breasts show on top of the torso, boots show on top of the shins, etc. But Godot's entire draw order is one of the most infuriating aspects of the engine. As I said above, it draws in a reverse vertical order, whatever's at the bottom of the scene's node list is drawn first and on top of other stuff.

Another annoying bug that popped up is that after fucking the orc, she'll remain stuck to the player.

On the bright side, she's properly attacking, being hit and disappearing if she dies instead of fainting.

After, what, 2 months?, the very first release of the game is now available!

https://parallelpapel.itch.io/bravesirknight

If you find any bugs, be sure to comment here or at the itch page above. Have fun!

* The problem with my spawners from the other day: the total number of nodes changed, and my code checked for a specific number of nodes before spawning. Basically, since the new graphic added one extra node, the code no longer worked.
* A couple of new clothes for the princess, one rag and one frilly dress in 3 colors

* I've also made some kinda good looking tiles, gonna put them on all stages now

* I also made an extra head for the princess, but it looks... Well, like shit, since all head parts expect a thin head shape. Here's what they look like - https://ibb.co/album/Vp09Vb
* Currently taking a look into sound effects and music, as thus far I've completely ignored both. Only after spending around an hour on Mixkit I saw the piece in their terms that "You must not (...) use an item in the context of adult content". Fucking hell... Freesound has some stuff, but the professional sites/services offer consistency, so sounds don't sound like "randomly downloaded off different sites".

So, besides Freesound, here's some other places that offer royalty free sounds, if anyone reading through this happens to be looking for that:

Artlist.io (through free trial)
https://www.zapsplat.com/
https://www.freesoundeffects.com/
https://freesfx.co.uk/
https://99sounds.org/

Managed to get some stuff done today:

* Made the princess' idle animation less wonky
* Made a proper death animation for the princess
* Added a toggle and working selection for player helmet
* Created and added UI to indicate player and princess health
* Created clickable button to bring the pause menu during gameplay


<- the UI. Nothing currently animated, but it does its job. The princess' health gets semi transparent if she's not on the screen

A number of weird flicker glitches are happening on the player animations. If you left-right too fast while with the helmet, you can pause the game and see the helmet on one side and the head on the other, as well as the torso facing one direction and the arms the other. No fucking clue on the cause yet. Case in point below:




Another weird bug is causing a function that only happens when the princess gets out of the screen to fire repeatedly while she's flickering from invulnerability after being hit. Had to make a check for the "is_invul" variable to make it stop, but seriously, some stuff is just beyond weird

Weekend edition, first posted over F95:

* Spent some time organizing the princess' Krita file, I'll probably release a copy of it and the Kobold when I release the first version of the game, so anyone can draw stuff for their own game and maybe distribute.
* Drew 2 more hair styles for the princess, one short (kinda inspired by Cure Black, might give it more length) and one that covers the eyes. The latter doesn't cover the ears, so it ends looking odd.
* I've set up a number of human colors for the princess' skin and hair, so the player can decide whether they'll want "inhuman" (elf, orc, furry-adjacent, whatever else I come up with) princesses or not. Skin variation below - hair variation is black, light-ish black, brown, redhead and blonde

I've also started feeling kinda directionless again, since I was drawing more stuff than actually needed and simply messing with customization options despite not needing to, so I've made a proper tasklist to work on:
[PRINCESS]
* Fix her hands
* Fix her idle animation
* Fix the layer order of her being carried animation (send the back arm behind the player)
* Tweak the being carried animation
* UI for her health (only show while she's being carried)
[OTHER]
* Draw 2 spears for the Spike Trap - ED3: Partially done. Drew one, with a metal tip. I did enjoy making the animation do a little "shake" once it fully extends
* Make an arrow shooting trap
* UI for player health
* Design an actually playable stage 1 - ED3: Partially done, the stage has about enough to "get" what you'll be seeing going forward. Should be trivial to clear under 2 minutes the first time around.
* Separate stage timer from Global (total) timer, so it can be reset properly - ED3: Done
[BIG SEX ANIMATION]
* Draw the fucking pieces already (been "promising" this for over 2 weeks now)
* Animate at least "From Behind" and "Mating Press" positions

[RANT TO SELF]
Regarding stage design, one thing to keep in mind is to also keep it simple. I don't need all enemy types, I don't need all the traps, I just need enough to slowly present the challenges. Present a challenge with little to no stakes, then amp it gradually. One failed jump makes you backtrack a bit, the next one forces you to backtrack more. Two jumps later, one where failure is a death.
[END RANT TO SELF]

I probably won't have much time to work on these things today or tomorrow (weekend fun, gotta unwind!), but it's good to list them out so I stop doing "whatever" and regain focus. Keep an eye on edits to this post.

EDIT1 - Been designing the first stage, messing with the enemy spawner, and came a cross a bug that I've yet to solve. Spawned enemies become invisible if you grab (rape) them. Trying to figure out how and why that's happening, because checking the Remote scene (a debug vision of the nodes), nothing has been modulated to Alpha 0 (full transparency), nor has anything's visibility been turned off.
- Turning on collision shapes for debugging, the entity completely vanishes, as if i had just called a destroy() or queue_free(), to completely remove it from memory. It's "as if", but since the node is still showing up, it's not being "destroyed properly". The most direct fix is never allowing the player to grab a spawned enemy, so this never happens, but I'll be damned if I don't figure out what the fucking fuck is going on, especially because it fucking used to work in previous versions.
- On spawn, it's also affecting other enemies already present. Jesus, what the fuck is going on
--- I've figured one of the problems, which was causing collision boxes to change shape (this was a problem because one of said boxes was the line of sight of the Archer kobold), was caused because the CollisionShape2D were not "Local to scene". Not sure if this is the "right way" things should be, but it took a lot of time for me to figure that. Still working on the "disappearing" problem above

EDIT2 - Well, turns out the problem was the fucking position. After testing with a different scene/spawning methods, I've saw the kobold in the "wrong" place. Being spawned, the enemy's actual position is a sum of its own + the spawner, something I had previously fixed but apparently commented again because of some problem or another
-- Anyway, the actual fix was changing this line, that positioned the kobold:
>> position = player_node.position + player_node.eoffset.position
into this
>> position = player_node.position + player_node.eoffset.position - get_parent().position
PROBLEM. FUCKING. SOLVED. My fucking god, that made me go in circles needlessly. Worst of all was having to deal with the collision thing not working, but at least I've found a way around that.

Despite what I've said in my previous post, I've actually began transferring the player textures to the Transform nodes. As a safeguard, I haven't deleted anything that is currently present and already working. Thus far, changing the textures of the player's facial features and bodypart colors is working perfectly. Also, instead of normal Arrays pointing to the textures, I've made new Dictionary variables. This means I no longer have to use a "match" functionality, which reduces written code a bit.
Further work is aligning them with the bones, checking if all animations are working fine, then finally remove old texture nodes and references to them in the code.

Should've spent time drawing parts for the princess, but did nothing. Blergh.

Today was also interesting because I've caught wind of Unity's extremely asshole announcement, where they want to charge 20 cents PER INSTALLATION from every developer that manages to break a threshold of 200k lifetime installs and 200k dollars revenue in 12 months. Oh, that'll apply to already released titles, if they broke the minimum requirement, they'll be charged starting Jan 1st 2024. I sure feel glad I've never got around learning it, the bloat was unbearable. I've spent a significant amount time today discussing the matter around Lemmy. If I had a boss, he'd be yelling at me for being unproductive. As I'm my own boss in this project, I say "count that as R&D time"
- Unity's blog detailing the idea - https://blog.unity.com/news/plan-pricing-and-packaging-updates
- Some of the backlash - https://www.eurogamer.net/unity-backtracks-slightly-on-plans-to-charge-developers-for-game-installs

With what I have right now, I could probably work on another game idea I've had for a while, that involves lot of sex, a more straightforward "catch and rape" type of game. Future idea, not gonna work on it anytime soon, gotta finish the current one first.

On a smaller note, I had shit sleep last night and need to buy some anti allergics. Hopefully I'll have a better night tonight