@jonathanwillner

This update was all about laying
the foundation for the circuit-building gameplay. While there aren’t a lot of
flashy new features yet, a huge amount of work went into the systems that make
the game possible.

Component Placement

The board can now place components directly onto the
grid.

So far you can place:

 Batteries
Wires
lights
Switches

Each component snaps cleanly to the grid instead of being
placed freely.

 

 Toolbar A toolbar was added to quickly switch
between components. Selecting a button now changes the currently selected
component, making it much faster to build circuits.

 

 I added Rotation but got rid of it because  it was really buggy

 

 Dynamic Grid The board now automatically sizes
itself based on the screen to supportWindows. Phones. Tablets, Web browsers without
having to creating separate versions of the game.

 

 Beginning the Wire System

The biggest milestone in this
update was starting the automatic wire connection system.Instead of every wire
looking the same, wires now detect neighboring components and determine how
they should connect. This system allows wires to change automatically as the
player builds to intersect with each other.

 

 Smart Component Tracking The board now stores
the actual component objects instead of just their names. This makes it
possible for components to remember things like: Position ,Rotation ,Power
state , Connection directions

Preparing the Power System The
groundwork was started for the power propagation.

·        
The game now has the beginnings of a system
that can spread electricity from batteries through connected wires to powered
components.

 

Made New Pixel Art

·        
Several new pixel-art sprites for the different
wire orientations  

 

Battery icon
Switch icon
Light icon

 

 

Bugs Fixed

Components spawning in the wrong location.
Toolbar selection not updating correctly.
Preview not changing when selecting a different
component.
Scene reference problems.
Component naming mismatches.
Grid placement errors.
Wire detection bugs.
Various script and inheritance issues.

What I got done today

Made the assets
for the different orientations of the wire

Component
Placement System

Finished the basic component placement system.
Components now spawn on the grid where the player
clicks.
Added support for:

🔋 Battery
➖ Wire
💡 Light
🔘 Switch

 

Component
Selection

Added toolbar buttons for selecting components.
Fixed GameManager communication between:

Toolbar
Board
Components

Players can now
choose what they want to build before placing it.

 

           Placement Preview System

Added a ghost preview system.

Now when selecting a component:

A transparent preview appears.
The preview follows the mouse.
The preview snaps to the grid.
Changing the selected component updates the preview.

 

i made the assets for the different components ik thay suck im not good at pixilart art or art

Goal: Create the foundation for the electricity puzzle game.✅
what i did today Chose Godot 2D as the engine.
Decided on a grid-based puzzle system.
Planned a simple flat + pixel art style.
Created the basic project structure.
Designed the gameplay concept:
designed Placeing the electrical components.

with the current Design
The player will:

Receive limited components.

Place them on a grid.

Connect electricity.

Solve puzzles.

i worked on getting the death and health system working cus thay broke agian than i adden the new level to the level select and fixed some bugs

Dev Log: Fixing NPC Door Navigation IssueProblemWhile testing the new NPC AI system, I noticed that enemies were able to find the correct path using the NavigationAgent3D, but they would get stuck when trying to walk through doors.The NPC was not failing to find a path. The navigation debug showed:Navigation map was readyPath count was validThe NPC had a target positionThis meant the problem was not with the NavigationAgent3D or the navigation mesh.InvestigationI tested multiple possible causes:Rebuilt the navigation meshChecked NavigationAgent3D settingsChecked the NPC movement codeChecked collision sizesChecked the NPC pathingAfter debugging, I found that the issue was caused by collision layers.The NPC and the door were using the same collision layer, causing the NPC’s collision body to interfere with the door collision. The navigation system could see a valid path through the door, but the physics engine was stopping the NPC from moving through it.SolutionI separated the collision layers so the NPC and the door no longer incorrectly blocked each other.After changing the collision settings:NPCs could correctly enter and leave housesNavigation paths continued workingDoors no longer trapped enemiesMultiple NPCs could navigate the level correctlyNew Level ProgressI the Current AI Features The NPC system now includes: NavigationAgent3D pathfinding Enemy chasing and a behavior Anger system based on player messages that NPC can respond to in the chat UIMultiple NPC support with name targeting i agian cant uplode a video

devlog Building the Next Level Today I made more progresson the game by adding a new AI npc and started working on a brand-new level. First,I fixed several bugs with command handling and NPC responses, Then I startedbuilding the new level for the game and began creating and placing some simplehouses around the map to make the environment feel more realistic. Then I plannedout where the NPCs and points of interest will be located inside and around thehouses. The Next Step is to Finish building the houses and add moreenvironmental details, create interiors so players can explore inside thebuildings, and add the NPCs so they can interact with the player as well as continuingto improve the AI so the npcs react naturally to what the player says and does,and keep testing and fixing bugs as development continues. and AI Improvements & New Dialogue System witch was focused on improving the AI and laying the groundwork for more immersive NPC interactions. AI Improvements Continued working on the enemy AI that reacts to what the player says. Improved the NPC anger system and fixed navmesh i can only add one video tho

i have given up on getting the stt to work cause the auido godot outputs is to hard for stt models to understand so im just going to do a text box

i cant do a video because it will casue a feedback loop Today I finally got a working voice-controlled
AI system inside my Godot project. The goal was to let the player speak
naturally to NPCs and have the game react in real time. First I set up a full
voice pipeline: with a Microphone input capture inside Godot  Real-time voice detection using audio
thresholds Automatic recording when the player starts speaking  Silence detection to stop recording  Exporting audio chunks as .wav files Sending
audio to Whisper (whisper.cpp) locally  Receiving
transcribed text for game logic This allows players to literally talk to the
game than i added the audio improvements At first, the audio was messy and hard
for Whisper to understand. The main issues were  Muddy frequencies, Missing clarity in speech ,
and Some words being cut off at the start  To fix this, I added audio processing directly
in Godot: using a Compressor to  balanced
loud/quiet parts of speech and a band-Pass Filter to removed low rumble + high
noise and Improve microphone sensitivity tuning. After these changes, the
speech became much cleaner and Whisper started producing more accurate
transcriptions.

 

made jumping work smother and am starting on ai thingy that when you say something reacts to what you said so if you say something mean it attacts and you can give it camands like go over thare or get me that item ect

the game isnt as laggy as it lookes in the video my wifi is just buns Today I revamped my enemy’s navigation system and got the NavAgent working properly again after a lot of debugging. Before this update, the enemies would either get stuck on walls or fail to properly detect paths, which made the AI feel broken and inconsistent during gameplay. The main issue came from how the that i wasn’t using a NavigationAgent3D and instead just making the enemy go to the player one issue i ran into was how velocity was handled in the enemy movement code. Once I corrected the movement logic to properly use get_next_path_position () and only apply navigation to the X/Z axis while keeping gravity separate and added the floor walls and barrel nodes to the nav region the enemies started moving smoothly again and actually path around obstacles instead of bumping into them. After fixing the movement system, I also cleaned up the enemy AI script to make it more stable. The enemy now: Finds the player using groups Uses NavigationAgent3D to calculate paths Chases the player correctly around walls Maintains gravity properly while moving Attacks when close to the player This made the enemy feel way more alive and less “robotic,” since it can now properly navigate the level instead of just walking into geometry. Overall, this was a big improvement to the AI system and a solid step toward making the enemies feel more intelligent and fun to fight. I also fixed an issue where if you were touching the enemy and shot it you would get damaged and not the enemy.

also it was 2 hours and 50 minets idk why it says 5 hours and 55 minutes it may have been something else as well. This update was all about adding the fps arms and getting them to work in my game Aswell as redoing the player health and death systems. I had to redo the health system, so I made it into a more proper system that tracks the player’s health and detects when it reaches zero. Once the player’s healthreaches zero, they die, and the game displays the dedicated death screen instead of just leaving the player in the world. Getting this working was notas simple as I expected. I ran into several issues while connecting the player script to the death screen. At first, Godot could not find the custom health class because I had the wrong type name. After fixing that, I ran into errors where the death screen function expected different arguments than I was providing. Later, I hit another problem where the game tried to call the deathscreen on a null instance because the node reference was not set correctly. Each error pointed me toward another part of the system that needed attention. Once I fixed the node references and cleaned up the function calls, the deathscreen finally appeared correctly when the player’s health reached zero. Although it took several debugging sessions with chat gpt I know I used ai sue me I had no idea what I was doing and now I kind of know what I am doing, I nowhave a much more reliable player death system. my recodeing software dosnt recod the game aprently i cant add video

i added hotbar to tired to make a paragraph

I built the first real version of my inventory system where items can be dragged between slots and now picked up from the world. The biggest change is that the inventory is no longer just UI — it actually connects to gameplay through item pickups and world objects.
The hardest part was getting Godot’s drag-and-drop system working correctly. At first, items would disappear or not register drops because I was clearing slots too early and missing the proper _get_drag_data() flow. I also had to fix mouse filtering so the slots would actually receive input.
After that, I added a simple world item system using an Area3D, so walking into the sword adds it directly into the first empty inventory slot. Wiring the inventory as a global group took a bit of trial and error, but it finally connects cleanly now.
Right now it’s still very basic — no stacking or hotbar yet — but the foundation is solid: items exist in the world, can be picked up, and moved freely between slots. This is the first step toward a full RPG inventory system.

this did not take 15h my hacktime is gliched Devlog — Switched from 3rd Person to First Person Camera System and added map
I switched my project from a 3rd-person camera setup to a full first-person controller, which meant completely removing the camera pivot system and rebuilding movement to feel correct without a visible character model guiding direction.
The hardest part was fixing movement and facing direction after the switch — my original system used camera-relative controls and a rotating model, but in first-person that broke everything and made movement feel backwards or disconnected. I ended up rewriting the movement to be cleaner and removing the dependency on camera-based rotation entirely.
It took a while to get the character to stop going the wrong way, but after removing the old camera logic, and the animations since thay were still expecting the third-person model rotation. the controller now works in first-person, with movement and animations aligned properly, and I can start adding combat and other features. the video is the third person camera not working well now the animations dont show so im going to try and fix the third persion camera and i made a video but i cant show it so

ok so this is a mix of my 3d godot game and my fantasy game idk why but i added dying animations to godot game and added sword and sword animations to fantasy game and debuged

i added player, animations,and deth