Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
(1 edit)

Hi, I just bought this dialogue system and I quite like it :)


Just wanted to comment to list a few issues I've had with setting up your dialogue system in my game. It's mostly about things that are hardcoded and that could do with being parameterised:

  • The camera node should be optional (I added ifs in the code to check if it's there)
  • Setting the camera in onready with a hardcoded path isn't great, a function to set it is better (in my game the scene changes and the camera doesn't always have the same path). In my game code I was just changing MSG.camera manually instead
  • There are a few sizes/offsets that are hardcoded in the singleton. Namely the y offset at which message bubbles are shown (it's 96 I think, which was way too much for my game with 16x16 tiles)
  • The global "G" reference should also probably not be hardcoded but instead be a variable that is set by the game. It's a bit weird otherwise to be forced to change how I manage my global singleton. That or some sort of API to get/set values to be accessible by MSG
  • There are other things hardcoded here and there that caused me issues but I don't remember them all

It would be really useful if there was an easy way to configure those things, or if they were at least in one place easy to customise (for example an MSG.Config object with variables inside?).

Those things could also be documented in the meantime, because I had to dig in the code to figure out why things weren't working.