I made a fork of SproutyDialogs that I call BrusselSprouty

[Snowpire]

Hey. I'm very new to Github and this is my first release here. I've been using SproutyDialog for my own game and made some big changes along the way. I decided to upload my changes in case anyone else found them useful. Mainly, conditionals in dialogue options, audio on dialog, an alternative previewer/debugger that can be toggled on and off. I made a video to demonstrate the changes: https://github.com/Snowpire/BrusselSprouty/tree/main

However, this is my first time committing anything to Github, and I don't know how everything works. I made some changes to the code, and (hopefully) some bug fixes. I know that you are supposed to be able to merge files and such to help developers with bug fixes, but I don't really understand how all of that works yet. Also, I got a big helping from ChatGPT Codex, so can't guarantee that all changes are clean, even though I tried to look over them.

Anyway, I hope I'm not stepping on any toes here, and that I'm doing this the right way.

[Vicente-G]

Hello @Snowpire tysm for sharing your work, if you are willing to contribute it to SproutyDialogs we'll be more than welcoming!

We usually expect contributions to come feat-wise, (baby steps!) but we could do an exception on this. Here's how:

• You would open a Pull Request (PR) with your fork, and provide a description on what are the features/fixes you are willing to bring in, you can filter them in a specific branch too for a cleaner PR.*
• We'll assess each of them through a Review, and provide you feedback so we can agree with implementations of said features.**
• When we have come to an agreement we can merge your changes in!

This will be a bit challenging though, as you worked quite a lot in our plugin ^-^' But we hope you can have the time to share this effort :)

(*) As you said you were new to Github I'll explain a bit more this point! In Github's UI when you are in your fork, it should show you a button to contribute to this repo. But that can be done with any of the branches you have in the fork. If there are features too specific to your use cases, you can remove them in another branch, and create the PR with this new branch instead.

(**) We need to agree in what is shipped into this plugin, as we maintain multiple versions, and care for the overall experience of all of our users, is not just plain gatekeeping, we have our opinions too though!

[Vicente-G]

Also you did fine with the fork, no worries, I forgot to answer ^-^'

Welcome to Open Source, I hope you like it!

[Snowpire]

Perfect! Appreciate your reply! Sure I will do it tomorrow. Whether you accept any changes or not, I'm still grateful for the opportunity to learn, and receive feedback! :) I trust your vision, don't worry about it.

[Vicente-G]

That's very cool! Looking forward to your PR :D