On Sale: GamesAssetsToolsTabletopComics
Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
Tags

$$$ Yarn Spin GUI $$$

A topic by VP created Feb 26, 2024 Views: 58 Replies: 3
Viewing posts 1 to 3

Hi Mattias, I was wondering..

If I paid $100 up-front, would you consider making a GUI for Yarn Spin please?

Basically, a text editor with check-box options to: create characters, items, variable-flags, images, ambient sounds, music etc - (all available Yarn Spin features/options) in a GUI tool - so all we have to do to create a game is: check the options we want to include, type the story-text, point to any images/sound files and click test/compile? This should make it easier to use and would eliminate any compile errors.

You could offer it as a separate helper-tool if you feel it would interfere with the appeal/style of the main yarn spin 2 engine.

I appreciate this is a major update and would require quite a lot of extra work on your part-  but maybe even a GUI for error-handling/debugging would be sufficient instead?

I'm finding it really difficult (impossible) to compile my game with a simple character, probably because I can't find the errors I've made - but I'm happy to pay for an autonomous solution if you can think of any - maybe it's just a case of me being more patient and getting to grips with yarn spin properly?

I also considered if it's simpler/possible to make a syntax-checker using sublime text - but maybe that's not really viable, because yarn spin games can span several text documents?

Thank you again!

OK, it already has a debugger - I only just figured out how to use it...

Instead of launching the yarnspin.exe, you need to right-click an empty space in your yarnspin.exe folder (don't right-click the actual yarnspin.exe) and select "open in terminal".
Now type

"./yarnspin"

(without the quotes) and press enter/return. It will notify you of any errors and tell you the line-number and the type of issue. Woohoo! I had no idea it could do this.

Developer

Ah, yeah, I am very happy that you got error messages working, it must have been so difficult to try and work out what was going wrong. I've tried to put in a decent amount of error checking, but it is also something I want to improve going forward.

I think if there's one good thing that comes of your struggles to get it to work, it is that I've realized I should be a lot clear about this in the documentation, and I will really improve this section, including screenshot of what is expected to show on screen and how to deal with errors!

Making a GUI or editor is something I've been thinking about (likely as a standalone Yarnspin Studio), but to be  honest, it is not something I have in my plans for anywhere soon. I have a lot of ideas for features to add to Yarnspin going forward, and having to maintain a visual tool for it will just make those much harder and more time-consuming, and I don't want to be slowed down like that. But I do think it would be a fun thing to make and a useful thing to have,  so I could see myself tackling it some day.

But hey, since this is free open source software, we can always hope that someone else decides they can't wait and starts making one - not very likely maybe, but we can hope :)

Perfect - thank you again. I think it's great the way it is, updating the tutorial to include a screenshot is a great idea. I agree, I would say it doesn't need a studio, especially given that the debugger is already so functional.