Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
Tags

I'm having a bit of trouble with 8-bit compatibility errors as well - in my case it's when playing around with barriers.  I can get a 'door' barrier to work but not a 'block' or 'block_path':

   stay_upstairs : block {
   
      location               = downstairs
      message                = You need to port your game before you can go downstairs!
      block_when             = still_porting
      show_blocked_exit      = true
   }
   
   stay_upstairs : block_path {
   
      from                   = landing
      to                     = downstairs
      message                = You need to port your game before you can go downstairs!
      block_when             = still_porting
      show_blocked_exit      = true
   }
   
   stairguard : door {
   
      from              = landing
      to                = downstairs
      key               = stairguard_key
      is_open           = false
      messages {
         bang_into_door                    = You need to port your game before you can go downstairs!
      }
   }

The 'block_path' example throws up the following error:

and the 'block' example throws up the following error:

Not sure what 'lion' and 'swim' mean here?

Hi Dee,

'Lion' and 'Swim' were placeholder error messages that I never got round to fleshing out.

The good news is that I've updated the error messages now, and they should also point to a line number.

'Lion' was an error message that should have informed you that the block_when (or block_when_not) conditions have to reference a regular boolean (that you can set true and false) rather than a dynamic boolean. This is down to the 8-bit game engine not supporting them. It should be easy to avoid using dynamic booleans in this context.

'Swim' is a little interesting because I don't see anything in your code that should trigger it. I've rewritten the message as this now.

Block condition invalid, supported conditions are:
      'block_when', 'block_when_not', 'block_when_carried',
      'block_when_not_carried', 'block_when_not_exists',
      'block_when_exists', 'block_when_worn', &
      'block_when_not_worn'.

but, as I say, in your included code, I don't see you not using one of those conditions.

When you see the (above) message, look at the line number of the error, and send me the block code that is failing (you can switch out any specific text that is secret of course).

Let me know how you get along.

Thanks Chris. I'll have another go and send you a code snippet if I still can't get it to work. 

Hi Dee,

Atop of the faulty error messages, there was an underlying bug in the exporter when the 'block_when' condition was used.

This is now fixed. Press the refresh button in your browser, and it should (hopefully) be working now.

Chris