home.social

#fartengine — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #fartengine, aggregated by home.social.

fetched live
  1. The is rolling along. I've been rebuilding the event system and it is getting close to working in the editor. In-Game on the other hand is just a cluster of spaghetti that I'll have to unravel.

  2. The website for the is live. Made using .

    It is what it is.

    What it isn't though is a fetish site.

    Unless awesome add-ons for make you thirsty

    fartengine.com/main.html

  3. devlog 26:

    - After 10+ hours, Godot is finally not crashing when it first loads the Fart Engine

    Proud of what I accomplished but I am mentally exhausted

  4. #FartEngine devlog 25: #GodotEngine #Godot4 #IndieDev #GDScript

    -Extensive refactoring of the Database Manager and Table Display Template, still in progress

    -Changed several class names and script inheritance to better organize the project

    -Began making flow chart of the entire project

  5. devlog 25:

    -Extensive refactoring of the Database Manager and Table Display Template, still in progress

    -Changed several class names and script inheritance to better organize the project

    -Began making flow chart of the entire project

  6. #FartEngine devlog 25: #GodotEngine #Godot4 #IndieDev #GDScript

    -Extensive refactoring of the Database Manager and Table Display Template, still in progress

    -Changed several class names and script inheritance to better organize the project

    -Began making flow chart of the entire project

  7. #FartEngine devlog 25: #GodotEngine #Godot4 #IndieDev #GDScript

    -Extensive refactoring of the Database Manager and Table Display Template, still in progress

    -Changed several class names and script inheritance to better organize the project

    -Began making flow chart of the entire project

  8. #FartEngine devlog 24: #GodotEngine #Godot4 #IndieDev #GDScript

    -Fixed a bug causing Godot to lag when loading map scenes in editor with too many FartEvents

    -Created a few new assets for the example game level 2

  9. devlog 24:

    -Fixed a bug causing Godot to lag when loading map scenes in editor with too many FartEvents

    -Created a few new assets for the example game level 2

  10. #FartEngine devlog 24: #GodotEngine #Godot4 #IndieDev #GDScript

    -Fixed a bug causing Godot to lag when loading map scenes in editor with too many FartEvents

    -Created a few new assets for the example game level 2

  11. #FartEngine devlog 24: #GodotEngine #Godot4 #IndieDev #GDScript

    -Fixed a bug causing Godot to lag when loading map scenes in editor with too many FartEvents

    -Created a few new assets for the example game level 2

  12. Going forward I'm going to use this thread for the #FartEngine devlog updates

  13. Going forward I'm going to use this thread for the devlog updates

  14. Going forward I'm going to use this thread for the #FartEngine devlog updates

  15. Going forward I'm going to use this thread for the #FartEngine devlog updates

  16. #FartEngine devlog 23: #GodotEngine #Godot4 #IndieDev #GDScript
    -modify player health command added

    -number input datatype can now be set to only allow positive numbers and to only allow integers

    -Events can now be pushed by player if flag is set

    -Improvements to modify player health functions

    All of the mechanics are now available to create level 2. My next task is to create the assets and build it

  17. devlog 23:
    -modify player health command added

    -number input datatype can now be set to only allow positive numbers and to only allow integers

    -Events can now be pushed by player if flag is set

    -Improvements to modify player health functions

    All of the mechanics are now available to create level 2. My next task is to create the assets and build it

  18. #FartEngine devlog 23: #GodotEngine #Godot4 #IndieDev #GDScript
    -modify player health command added

    -number input datatype can now be set to only allow positive numbers and to only allow integers

    -Events can now be pushed by player if flag is set

    -Improvements to modify player health functions

    All of the mechanics are now available to create level 2. My next task is to create the assets and build it

  19. #FartEngine devlog 23: #GodotEngine #Godot4 #IndieDev #GDScript
    -modify player health command added

    -number input datatype can now be set to only allow positive numbers and to only allow integers

    -Events can now be pushed by player if flag is set

    -Improvements to modify player health functions

    All of the mechanics are now available to create level 2. My next task is to create the assets and build it

  20. devlog 22:
    -autoload name changed from FARTENGINE to FART
    -added camera control script
    -added 4 new commands, all control camera movement
    -Improvements made to the process for adding new commands
    -Updated project on github

    Up next: Allowing player to push events

  21. #FartEngine devlog 22: #GodotEngine #Godot4 #indiedev #GDScript
    -autoload name changed from FARTENGINE to FART
    -added camera control script
    -added 4 new commands, all control camera movement
    -Improvements made to the process for adding new commands
    -Updated project on github

    Up next: Allowing player to push events

  22. I think it might be time to make the first for the .

    Does anyone out there have any tips for me? I'm not sure where to start.

  23. I think it might be time to make the first #Tutorial for the #FartEngine.

    Does anyone out there have any tips for me? I'm not sure where to start.

    #GodotEngine4 #IndieDev

  24. #FartEngine dev update 21: #GodotEngine #Godot4 #indiedev #GDScript

    -Events can now damage player when touched, you can set the knockback force, damage amount, and delay before event can damage player again.

    -Player can take damage, will flash and be invulnerable, the time for both can be set in character table.

    -Player death Game State added.

    -Menu BGM can now be set in Menu table.

    -BGM is now controlled by audio engine.

  25. dev update 21:

    -Events can now damage player when touched, you can set the knockback force, damage amount, and delay before event can damage player again.

    -Player can take damage, will flash and be invulnerable, the time for both can be set in character table.

    -Player death Game State added.

    -Menu BGM can now be set in Menu table.

    -BGM is now controlled by audio engine.

  26. #FartEngine dev update 21: #GodotEngine #Godot4 #indiedev #GDScript

    -Events can now damage player when touched, you can set the knockback force, damage amount, and delay before event can damage player again.

    -Player can take damage, will flash and be invulnerable, the time for both can be set in character table.

    -Player death Game State added.

    -Menu BGM can now be set in Menu table.

    -BGM is now controlled by audio engine.

  27. #FartEngine dev update 21: #GodotEngine #Godot4 #indiedev #GDScript

    -Events can now damage player when touched, you can set the knockback force, damage amount, and delay before event can damage player again.

    -Player can take damage, will flash and be invulnerable, the time for both can be set in character table.

    -Player death Game State added.

    -Menu BGM can now be set in Menu table.

    -BGM is now controlled by audio engine.

  28. I keep trying to find a quick way to describe the Add-On on for and so far, the best description I've been able to think of is, "it's a hat on a hat".

    It sits on top of Godot and currently handles the game database, saving, loading, event interactions, 2D sprite creation, dialog, and much more.

    My goal is to make it where one can create a 2D game writing little to no code.

  29. I keep trying to find a quick way to describe the #FartEngine Add-On on for #GodotEngine4 and so far, the best description I've been able to think of is, "it's a hat on a hat".

    It sits on top of Godot and currently handles the game database, saving, loading, event interactions, 2D sprite creation, dialog, and much more.

    My goal is to make it where one can create a 2D game writing little to no code.

  30. devlog 20:
    I've been fairly productive the past few days.

    -Removed shadows because the shader was not working
    -Fixed stutter when interacting with events
    -Fixed bug where event does not run "Immediate" commands when too many are trying to activate at the same time
    -Improvements to event editor script
    - changes to event editor layout
    -Started WIP event option to damage player when touched (which is what prompted all of the above changes)

  31. #FartEngine devlog 20:
    I've been fairly productive the past few days.

    -Removed shadows because the shader was not working
    -Fixed stutter when interacting with events
    -Fixed bug where event does not run "Immediate" commands when too many are trying to activate at the same time
    -Improvements to event editor script
    - changes to event editor layout
    -Started WIP event option to damage player when touched (which is what prompted all of the above changes)

    #GodotEngine4 #GodotEngine #IndieDev

  32. devlog 19: I've given up on custom menus at this time. Users will need to use and to display information to the player.
    Instead, I've decided to make a test level. It is simple. Player finds 30 rupees and gives them to a chest that will give you a knife to open a gate.

    As of now I can officially say that you can make a 2D game using the Fart Engine add-on for Godot

    Tonight I celebrate!
    Tomorrow I start on the phase 2: more stuff so you can make a GOOD game

  33. #FartEngine devlog 19: I've given up on custom menus at this time. Users will need to use #GodotEngine and #GDScript to display information to the player.
    Instead, I've decided to make a test level. It is simple. Player finds 30 rupees and gives them to a chest that will give you a knife to open a gate.

    As of now I can officially say that you can make a 2D game using the Fart Engine add-on for Godot

    Tonight I celebrate!
    Tomorrow I start on the phase 2: more stuff so you can make a GOOD game

  34. #FartEngine devlog Day 18: it's been a while, but I've not given up. Today I fixed the bug that broke conditions, and I continued working on the input form that will be used to select values to display in-game, which will enable users create custom menus (hopefully). It's a big chunk and one of the last big peices needed to create a full game, even if there isn't much you can do in the game (yet).

    #GodotEngine4 #GodotEngine #IndieDev

  35. devlog Day 18: it's been a while, but I've not given up. Today I fixed the bug that broke conditions, and I continued working on the input form that will be used to select values to display in-game, which will enable users create custom menus (hopefully). It's a big chunk and one of the last big peices needed to create a full game, even if there isn't much you can do in the game (yet).

  36. #FartEngine devlog Day 18: it's been a while, but I've not given up. Today I fixed the bug that broke conditions, and I continued working on the input form that will be used to select values to display in-game, which will enable users create custom menus (hopefully). It's a big chunk and one of the last big peices needed to create a full game, even if there isn't much you can do in the game (yet).

    #GodotEngine4 #GodotEngine #IndieDev

  37. #FartEngine devlog Day 18: it's been a while, but I've not given up. Today I fixed the bug that broke conditions, and I continued working on the input form that will be used to select values to display in-game, which will enable users create custom menus (hopefully). It's a big chunk and one of the last big peices needed to create a full game, even if there isn't much you can do in the game (yet).

    #GodotEngine4 #GodotEngine #IndieDev

  38. #FartEngine devlog Day 16 & 17: I did not work on the engine on either day. I spent most of my time watching Dance moms (trying to shut my brain off) or watching Josh Strife Hayes play the worst MMO he can find. I prefer to think of it as research as opposed to being uninspired to do any actual work

    #Godot4 #GodotEngine #IndieDev

    youtube.com/playlist?list=PLEp

  39. devlog Day 16 & 17: I did not work on the engine on either day. I spent most of my time watching Dance moms (trying to shut my brain off) or watching Josh Strife Hayes play the worst MMO he can find. I prefer to think of it as research as opposed to being uninspired to do any actual work

    youtube.com/playlist?list=PLEp

  40. #FartEngine devlog Day 16 & 17: I did not work on the engine on either day. I spent most of my time watching Dance moms (trying to shut my brain off) or watching Josh Strife Hayes play the worst MMO he can find. I prefer to think of it as research as opposed to being uninspired to do any actual work

    #Godot4 #GodotEngine #IndieDev

    youtube.com/playlist?list=PLEp

  41. #FartEngine devlog Day 16 & 17: I did not work on the engine on either day. I spent most of my time watching Dance moms (trying to shut my brain off) or watching Josh Strife Hayes play the worst MMO he can find. I prefer to think of it as research as opposed to being uninspired to do any actual work

    #Godot4 #GodotEngine #IndieDev

    youtube.com/playlist?list=PLEp

  42. #FartEngine devlog Day 15: I made changes to the List datatype in preparation for using it in the datatype display node. There are now flags to show/hide labels, a checkbox for each index, the datatype selection, and also the index number or name will show in the title bar of each entry. This still allow me to modify the list item while still using the same functions to access data.

    #GodotEngine4 #GodotEngine #IndieDev

  43. devlog Day 15: I made changes to the List datatype in preparation for using it in the datatype display node. There are now flags to show/hide labels, a checkbox for each index, the datatype selection, and also the index number or name will show in the title bar of each entry. This still allow me to modify the list item while still using the same functions to access data.

  44. #FartEngine devlog Day 15: I made changes to the List datatype in preparation for using it in the datatype display node. There are now flags to show/hide labels, a checkbox for each index, the datatype selection, and also the index number or name will show in the title bar of each entry. This still allow me to modify the list item while still using the same functions to access data.

    #GodotEngine4 #GodotEngine #IndieDev

  45. #FartEngine devlog Day 15: I made changes to the List datatype in preparation for using it in the datatype display node. There are now flags to show/hide labels, a checkbox for each index, the datatype selection, and also the index number or name will show in the title bar of each entry. This still allow me to modify the list item while still using the same functions to access data.

    #GodotEngine4 #GodotEngine #IndieDev

  46. devlog Day 14: I didn't do much, I added an option to use a checkbox instead of a radio button for the boolean datatype. No plans to let the user change the default. I plan to use checkbox for certain input forms. This is the first step towards custom menus

  47. #FartEngine devlog Day 14: I didn't do much, I added an option to use a checkbox instead of a radio button for the boolean datatype. No plans to let the user change the default. I plan to use checkbox for certain input forms. This is the first step towards custom menus

  48. devlog Day 13: Not much done today. I mapped out how I want the Fart Display nodes to look and function.

  49. #FartEngine devlog Day 13: Not much done today. I mapped out how I want the Fart Display nodes to look and function.

  50. devlog Day 12: I started to map out what the FartDisplay node input form will look like. I also made improvements to the event save information (breaking compatibility with save files from previous versions) as well as improvements to the edit save file menu that now allow user to view and edit all save file data


  51. #FartEngine devlog Day 12: I started to map out what the FartDisplay node input form will look like. I also made improvements to the event save information (breaking compatibility with save files from previous versions) as well as improvements to the edit save file menu that now allow user to view and edit all save file data

    #GodotEngine4 #GodotEngine #IndieDev
    #Godot4

  52. devlog Day 11: With all of the bugs fixed (at least the ones that one found that are worth the time to fix), today I added a new event command. You can now change the value of dialog options. When the player is given dialog choices, the button that is clicked will change the value of that dialog option to true. This allows the event page to change and the event can progress. Before today, that was a one way deal.
    1/2

  53. #FartEngine devlog Day 11: With all of the bugs fixed (at least the ones that one found that are worth the time to fix), today I added a new event command. You can now change the value of dialog options. When the player is given dialog choices, the button that is clicked will change the value of that dialog option to true. This allows the event page to change and the event can progress. Before today, that was a one way deal.
    1/2

  54. devlog Day 10: I did not make any progress on the engine but I did finally upgrade my laptop's operating system from to

    There are some irritating things but overall it's much better.

  55. #FartEngine devlog Day 10: I did not make any progress on the engine but I did finally upgrade my laptop's operating system from #Windows11 to #LinuxMint

    There are some irritating things but overall it's much better.
    #IndieDeveloper

  56. devlog Day 9: Slept most of the day and felt like I was twice as heavy as normal. Watched a few C programming tutorial videos but otherwise was unproductive

  57. #FartEngine devlog Day 9: Slept most of the day and felt like I was twice as heavy as normal. Watched a few C programming tutorial videos but otherwise was unproductive

  58. devlog Day 8: I did not write any code. I did "field research"... Ok, fine, you got me. I went to Disney springs and played Pokémon Go with a friend

  59. #FartEngine devlog Day 8: I did not write any code. I did "field research"... Ok, fine, you got me. I went to Disney springs and played Pokémon Go with a friend