!Munchy A clone of a classic maze game

Thanks for identifying the problem I wonder why its different was DIM LOCAL added to BASIC later?.

Found some info.

HTH.

Chris , David

Can you download MunchyNJ once again I have changed all the DIM LOCALs to standard DIMs I have crunched it because you really need the speed when in the desktop and also I would like to know that the final version works. fingers crossed :-)

Also updated the res file and removed the USB joystick

Can you download MunchyNJ once again I have changed all the DIM LOCALs to standard DIMs … I would like to know that the final version works.

That works on OS4.39.

Thanks again for your help.

I will leave MunchyNJ.zip in place for people that use older systems.

I assume its playable when using RPCEmu is the speed OK?

I wouldn’t recommend trying to load USBJoystick in a game !Run file. If someone has a suitable machine (anything which can run a new enough USBDriver module) and a joystick, then it is up to them if they want to run it. A game should issue a XJoystick_Read SWI and see if something responds.

The BASIC issue in 4.39 just makes me wonder why people bother to run or support it!

I assume its playable when using RPCEmu is the speed OK?

It is perhaps a bit on the slow side on RPCEmu, but given the speed of my fingers that might be good thing. VRPC might be faster. I’m not into games, I only got involved here to see what the problem might be.

Anyway it is just as well the speed question was asked as I found another show stopper on the newly rebooted OS4.39. The ProgInfo Toolbox module needs to be explicitly RMEnsured as UnPlugTbox has done its stuff, the latest ROL Toolbox module versions being in !System in this case. And the same for any other Toolbox modules Munchy requires.

Oops forgot about that it’s been a while since I used the toolbox I’ll update the zip file later. Thanks

RISC OS Select 4.39 got to version 1.29 (08-Jan-2004) of BASIC but in the select fork.

Meanwhile RISC OS 4.03 was at BASIC version 1.20 (15-Sep-1999) but when RISC OS 5.01 appeared it was at BASIC V Version 1.34 (02-Dec-2002) and the DIM LOCAL was added in version 1.30 (23-Apr-2002) in the Castle fork. The Select fork has not yet added this.

Version 1.30 notes:

• The new DIM LOCAL statement has been added:
  Syntax: DIM <numeric variable> LOCAL <numeric expression>

It works on 4.39 but the sound only appears on the credits screen. The text on the credits screen appears and disappears as different menu items are hovered over.

Interestingly, the Reference Manual says that it was added in 1.34. I’m not sure whether this was a typo, or whether 1.30 was never released to the public (does it predate going open source?).

Edit: It would help if I fully read your post before commenting! If OS 5.01 came with 1.34 then it seems that my ‘guess’ was probably correct.

DIM LOCAL, BASIC 1.30

The Select fork has not yet added will not be adding this.

FTFY.

The person ¹ who wrote DIM pointer% LOCAL size% sent me a copy of that source when I was in the early stages of writing Basalt on Select. I included DIM LOCAL pointer% size% so that it could be used in programs for both forks. It uses the trick of faking a local array.² A consequence of this is that END= can be used, which I notice from David’s link is a limitation on the ‘real’ BASIC. ;-)

¹ I am unsure whether it is right to say who without their permission.

² This trick can be implemented in BASIC only, but it is a bit complicated.

I have just uploaded version 1.02 of Munchy
There are no main changes to the operation of the game.

Hopefully this version should work on all RISCOS machines.
Although my main target machines were newer hardware running RO5
I was amazed that it worked OK on the Iyonix to be honest.

The changes are:-

V1.02 Munchy Checks for joystick on startup
if false do not use?

Added RMensure toolbox modules

Removed rmensure of USBjoystick

Removed DIM LOCAL as earlier versions
of BASIC do not support it.

Removed INKEY0 stops keypresses being passed
onto the WIMP replaced with own debounce routine

Get it here:-
www.mbelect.co.uk/RISCOS

Sounds like we need an easy to read list of what was introduced in what version. Plus, is there an easy way to tell the current version of BASIC? Isn’t it something like REPORT$ before an error has happened?

Hopefully this version should work on all RISCOS machines.

Oops, bad timing. Was just about to post another bit of OS4.39-ness.

Munchy uses a Sassoon font, but Sassoon is not present as standard on OS4.39. An Undefined Font Handle error occurs after all lives have lost. Once Sassoon is installed the game does continue.

With the Sassoon font installed, Munchy 1.02 is OK on OS4.39, as briefly tested.

but Sassoon is not present as standard on OS4.39.

TheF…? It’s not in Boot Fonts, where it’s been since forever?

This game is sure bringing up some quirks!

I would have thought it would crash on start up because
the Sassoon font is used in the score table?

So do I change all the fonts used to Trinity or can I include the Sassoon font in my zip file? and then people could install if needed?.

TheF…? It’s not in Boot Fonts, where it’s been since forever?

Create an OS that fits the environment, go away and thus allow “others” to extend it – in the same size environment.
“Others” extend and embellish more – in the same size environment and run out of space so drop little used frills.

Neighbours use newer and bigger property and wonder what the space problem is all about.
Neighbours try to fit their newer OS back into old property…
…give up and leave property vacant.

So do I change all the fonts used to Trinity or can I include the Sassoon font in my zip file?

Oooh, licence?
Probably better to ask that the font is added to the System download available on the ROOL download pages.

I think I will leave Munchy as it is if someone is that driven to run it on OS4.39 Im sure they are capable of tracking down their own version of the font needed.
The games runs fine on RO5 which it the OS I used to develop the game on.

So do I change all the fonts used to Trinity or can I include the Sassoon font in my zip file? and then people could install if needed?.

Sassoon may be present in VRPC, I have had a look at the installer and it was present in the Mac VRPC OS4.39. I no longer have any working Windows VRPC OS4.39 to check. My OS4.39 Sassoon free RPCEmu installation is from my long gone RiscPC and the Select 3i4 CD.

Many Thanks for everyones help in this quest :-)

Munchy uses a Sassoon font, but Sassoon is not present as standard on OS4.39.

Sassoon is present in the HardDisc4 downloads from this site.

Munchy uses a Sassoon font, but Sassoon is not present as standard on OS4.39.

Sassoon is present in the HardDisc4 downloads from this site.

Which is where the copy installed onto OS4.39 came from.

Sounds like we need an easy to read list of what was introduced in what version.

There is one in the BBC BASIC Reference Manual Issue 2 Appendix I.
However, I do not think it is freely available, and it is not listed in the ROOL Store except as part of the DDE.edited to remove as incorrect

Plus, is there an easy way to tell the current version of BASIC? Isn’t it something like REPORT$ before an error has happened?

*Help BASIC
REPORT$ just gives eg “ARM BBC BASIC V © Acorn 1989”.

There is no reason that I know of why the most recent BASIC modules cannot be installed and used on RO4 systems. They are available for RO4 in the PlingSystem ‘System Resources’ on the Miscellaneous Downloads page. The BASIC modules are in !System.310.Modules, and seem to work happily from there on RO4. Indeed, the whole download is designed to be used in this way, but I have not checked if there are any consequences of doing that.

I have an obey file called !BASICload in my RO4.39 PreDesk, which contains:

*RMEnsure Basic   1.81  RMload System:Modules.BASIC
|*RMEnsure Basic64 1.81  RMload System:Modules.BASIC64

There have been several improvements and bug fixes to BASIC since the RO4 1.29 version. Until later versions are generally used, developers will be restricted, and some bug diagnosis can be very difficult (eg aborts at a rubbish line number).