Adventuron: Creating An 8 Bit Game With Graphics Tutorial

Hello,

I recently created a new tutorial for Adventuron based on a small “game” I created a while ago. The tutorial takes between 30 minutes and 60 minutes. Add on another 10 minutes if you want to export your game to ZX Spectrum Next.

https://adventuron.io/documentation/tutorial-a.html

Be aware this is not literary IF … to be honest, it’s barely puzzle-based TA. Adventuron is quite capable of narrative IF, but I am not sadly.

This tutorial game, is mostly meant as an introduction to the mechanics of building 8-bit style text adventures.

(Cave of Magic graphics by Ricardo Oyón)

Chris

9 Likes

i dont understand 'Adventuron ’ is for what exactly?

i thought this was a tutorial? ’ Adventuron: Creating An 8 Bit Game With Graphics Tutorial’

title should say what this thing is

anyway need exampes of what this creates all that matters before anything else

im very confuse by what this is, pls link examples of what this creates all that matters

Adventuron is an adventure authoring system. If you follow the tutorial, you will be able to see that.

Adventuron is a full-blown language. The editor runs in your browser and allows you to develop a game and test (or play) it at the click of a button. The editor includes syntax colouring, code hints, auto-completion and so on, just like any modern integrated development environment (IDE). When you’ve finished developing your game, you compile it to a single HTML file. The compiled file includes the Adventuron interpreter and your game data. Anybody can then play your game on any device that has a browser, including mobile phones, although games with graphics don’t leave much room (if any) for the text once the phone’s virtual keyboard takes up half the screen real estate.

There are lots of Adventuron resources out there if you care to look. This tutorial is one of several that Chris has prepared. If you follow the tutorial, you can see what Adventuron is and how to use it.

At the time of writing, at least 85 games have been published using Adventuron. There have been four game jams on itch.io. The most recent one had 7 entries and is currently going through the judging phase. There are 6 days left for judging. Most of the games are very good. When you consider that some of the games are written by first-time authors, that is very high praise indeed for Adventuron.

To play the games from this jam, see https://itch.io/jam/next-adventure-jam/entries

1 Like

Is it possible to write Adventures in Adventuron in languages other than English?

Jens

I know there’s a couple of people making Adventuron games in Spanish at the moment.

Most definitely. Natively, it supports English and Spanish, but providing the grammar is similar to English, I don’t see why other languages can’t be supported. In the themes section, you can override all the predefined system messages. Some verbs like GET, DROP, INVENTORY, SAVE and LOAD are hard-coded, but these can be supplemented by your own. Languages like French, German, Italian, Portuguese and so on should be easy to do.

It’s not so easy and obvious, especially for the French. There is, to my knowledge, no simple way to translate the directions of the compass: north, south, east etc… But this is a detail, because there are other problems related to syntax and grammar which are difficult to solve, for predefined system messages, if you are a bit demanding with that.

I think Garry was right that most system messages are easy to redefine, but language support (currently) has to be supported at system level (as Spanish is).

A French translation is on the way, and I’ll aim to have it in place in the few weeks.

Any chance that you might put German on your list (if there is a list :slight_smile: ) of translations?
Jens

1 Like

I disagree with you and Garry. All messages with ‘${entity}’ are problematic because of the definite, indefinite and quantifying articles in the French language.
Translation with a language like Inform 6 is complex and not always satisfactory. Just because it says it can be, doesn’t mean it is. Yet this language offers many more possibilities than Adventuron.

I don’t necessarily think that ${entity} is destined for bad article representation in French. There will be bespoke code for French to ensure this is correct, because each supported language is not just a lookup table of messages but a whole host of parser settings and textual presentation decorations.

Of course, but there needs to be demand.

indefinite/quantifying and definite articles in French, and their uses:
   ""       ""     # 0 Julia
   "une "   "la "  # 1 pomme     / apple
   "un "    "le "  # 2 dé        / dice
   "des "   "les " # 3 pommes    / apples
   "de la " "la "  # 4 confiture / jam
   "du "    "le "  # 5 sucre     / sugar
   "une "   "l'"   # 6 orange
   "un "    "l'"   # 7 oeuf      / egg
   "de l'"  "l'"   # 8 eau       / water

Something like that might be nice:

objects {
   pomme : object "pomme" indefinite = "une" definite = "la" ; 
}

But you’re the one who knows, and now I’m shutting up.

For each supported language, objects that are defined with articles have a formula applied to transform from indefinite to definite articles plus adventuron lets them be set manually.

I’ll let you know once the first French version is available. For sure it will need refinement.

Adventuron tells me that foreign-language support is more complicated than I realised. It sounds like he’s working on French support, then possibly Italian. Auraes would be a good one to test the French version.

If you yell loud enough, I’m sure you can get German support thrown in too.

As for me, I’m hanging out for the Australian version. :laughing:

Australian support indeed would be bonzer.

1 Like

I’m not so sure about that. I have experience translating the Inform 6 library into French, and I am aware of the many problems that will fall like a hailstorm. I’m not sure I want to, or have time for this.

I have faith in you, my friend. I believe French is your native language, you are a good tester and you’ve written games in Adventuron. That’s a good combination for testing the French version when it becomes available.

I get a compilation error with the file exported to DAAD. In /8 and /9 I should, it seems to me, have BEAN instead of 1 and 2.

DAAD Reborn Compiler Frontend 0.20 © Uto 2018-2020
Reading TEST.DSF
Checking Syntax…
#EXTERN’ “MLV_P3.BIN” processed.
301:56:TEST.DSF: Noun not defined: “1”.

Line 301: /8 1 1 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 1 _

objects {
   mouse    : object "* A tiny mouse" at = "loc9" ;
   key      : object "* A silver key" ;
   axe      : object "* An axe" at = "loc5" ;
   mother_1 : scenery "* Mother is here" at = "loc3" ;
   children : object "* The Children, Peter and Mary, are here." at = "loc12" ;
   giant    : scenery "* The --- G I A N T ---" at = "loc11" ;
   egg      : object "* The GOLDEN EGG" at = "loc11" ;
   bean_1   : object "* A bean" at = "loc3" ;
   bean_2   : object "* A giant beanstalk" ;
   door_1   : scenery "* An open door" ;
   door_2   : scenery "* A broken door" ;
   mother_2 : scenery "* Mother is here holding the GOLDEN EGG." ;
   mother_3 : scenery "* Mother is here with THE CHILDREN." ;
}
/OBJ

/0     252  1   _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _    _     _
/1     7    1   _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _    MOUSE _
/2     252  1   _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _    KEY   _
/3     3    1   _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _    AXE   _
/4     1    1   _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _    _     _
/5     10   1   _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _    CHILD _
/6     9    1   _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _    _     _
/7     9    1   _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _    EGG   _
/8     1    1   _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _    1     _
/9     252  1   _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _    2     _
/10    252  1   _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _    _     _
/11    252  1   _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _    _     _
/12    252  1   _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _    _     _
/13    252  1   _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _    _     _

Is it legal to have a bean_1: “object” and a bean_2: “scenery”?