A proper debugger for Scripts

[KakiDev 0]

Having a proper debugger would be great, I spent a few hours the other day printf-debugging my implementation of behaviour trees, and being able to step through the code step by step would have made this a lot easier and saved me a lot of time.

[Neffarion 486]

 

[Aeglen 294]

Idk what your code looks like but I'd advise avoiding lots of little tree-leaf-node files for every step, no matter how leet some people say it feels to have such "organised" code, imo it often results in a time consuming mess.

[KakiDev 0]

2 hours ago, Aeglen said:

Idk what your code looks like but I'd advise avoiding lots of little tree-leaf-node files for every step, no matter how leet some people say it feels to have such "organised" code, imo it often results in a time consuming mess.

Yeah, I think they can help a lot, but if you overuse them it quickly becomes worse than if you didn't use them at all.

3 hours ago, Neffarion said:

 

Thanks a lot, I feel like that should be turned into an official guide, I can't emphasize enough how helpful a debugger can be, it can really make your life a lot easier.

Coming from C++ and Rust, so I had no idea that something like

-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=12345

even exists.

[KakiDev 0]

 Tried it out, works fine, doesn't break on exceptions though, I assume thats because they are caught by DreamBot.

Piece of advise for Linux Users:
You can set "Before Launch" tasks in IntelliJ, tell it to build the artifact and run a .sh (Run External Tool) with the following content:

cmd="java -Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=12345 -jar ~DreamBot/BotData/client.jar"
eval "${cmd}" &>/dev/null & disown;

This will start DreamBot as a background process, so you don't have to manually start it. You can also use this to build a Run config that will build the jar and start DreamBot.

[xyz111 81]

15 hours ago, Aeglen said:

Idk what your code looks like but I'd advise avoiding lots of little tree-leaf-node files for every step, no matter how leet some people say it feels to have such "organised" code, imo it often results in a time consuming mess.

Wouldn't the ideal strategy vary with each situation? Have you read "The Art of Unix Programming"? It promotes the idea of writing code that's straightforward, clean, and modular, making it easier to upkeep and comprehend. While it's true that the initial setup can take time, the advantages, such as reduced likelihood of bugs due to less code duplication and enhanced readability, often outweigh the drawbacks

[camelCase 231]

45 minutes ago, xyz111 said:

Wouldn't the ideal strategy vary with each situation? Have you read "The Art of Unix Programming"? It promotes the idea of writing code that's straightforward, clean, and modular, making it easier to upkeep and comprehend. While it's true that the initial setup can take time, the advantages, such as reduced likelihood of bugs due to less code duplication and enhanced readability, often outweigh the drawbacks

you sound like a dork but yeah aeglens out of his mind like always.

[xyz111 81]

9 hours ago, camalCase said:

you sound like a dork but yeah aeglens out of his mind like always.

Fair point 😂