#4 Devlog - Final
I made everyting work. i made config and save button work and you can now add config or save it from other people. this is end of the project you can download it on my github ;)
Log in to leave a comment
#4 Devlog - Final
I made everyting work. i made config and save button work and you can now add config or save it from other people. this is end of the project you can download it on my github ;)
Log in to leave a comment
#3 Devlog - Working UI
In this devlog, I focused on making the UI I created earlier fully functional.
Everything is working exactly as intended — the clicker can register up to 50 clicks per second without any issues.
The only thing I still need to improve in the next devlog is adding user configuration support, allowing users to save their own configs.
Aside from that, everything will be finished and ready.
Log in to leave a comment
#2 Devlog - UI
in this devlog i made simple ui for the project ;)
Log in to leave a comment
#1 Devlog – C# AutoClicker
This is a simple auto clicker written in C# using Windows API.
It runs in the console and allows the user to set a global hotkey that toggles left mouse clicking at 13 clicks per second.
This version is a prototype of a bigger project.
The main release is planned to have a full GUI, this console app was made to test core functionality first.
Key Points
Global hotkey (works system-wide)
13 CPS using a timer
Toggle ON/OFF
Uses SendInput from user32.dll
Development time: around 5 hours (new in c#)
Most of the time went into learning Windows API and hotkey handling
Log in to leave a comment
In this final stage, I focused on the server logic. It was quite challenging, but I managed to get it done. I even pulled an all-nighter haha. I also improved the index file a bit and updated some commands I had added earlier, but everything works perfectly. I don’t remember if I mentioned it before, but I removed deploy-commands and integrated it into the index because it was a bit overkill. btw. interactionCreate.js took about 800 LINES in peak but i optimised it
Below, I’m sharing a video showing how it all works. Thank you, everyone! ;) (Idk why i made utils folder but this is my musthave in every project) I know it’s too long devlog. in case of anything, cut my time
Log in to leave a comment
In an earlier devlog, I wrote that I had started working on the code architecture design but that was just prototype. I’ve finished it. I wrote a complete code for events and all functions. It’s not the giveaway logic yet, but the code turned out really well. It was a long session because I’m not a vibecoder and I don’t use ready-made sources; I really want to dive into these things.
I also added a cool index.js that automatically detects issues, loads events and commands, so you don’t have to do anything—everything happens automatically. Also i made “frontend” for giveaway command. now im going to make logic for giveaways
Log in to leave a comment
First Advanced Setup ;)
Set up a Discord.js bot using Node.js and dotenv for environment variables.
Created a structured command handler: commands are organized in folders, loaded dynamically into a Collection.
Implemented permission checks for commands to restrict access to admins.
Added logging for loaded commands and bot login status.
Created a function to deploy slash commands automatically on startup, with proper checks for client, commands, and environment variables.
Fixed issues with client.commands being undefined during deployment by passing the client object correctly and checking the collection size.
Ensured interaction handling works only in servers and replies gracefully on errors.
Consolidated code for clarity: removed duplicate requires, merged duplicate functions, and improved readability. But this is all a prototype code so it will work bad and it took not enough time
Added optional deploy-on-start feature controlled by an environment variable.
Log in to leave a comment
In the first stage, I started creating the index.js file for the bot, but in the end I decided to skip it. In the next stage, I will increase the bot’s level of advancement and divide the project into folders so that programming is more enjoyable for me and the entire project structure and code are better written and more organized.
Log in to leave a comment