Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
Tags

Adventuron website feedback

A topic by sunteam created Jun 03, 2020 Views: 275 Replies: 19
Viewing posts 1 to 9
Submitted

Just a few things I noticed:

In the documentation, part 2.20 reads "set of syste mresonse messages"

Also, there doesn't seem to be a clear link to the manual from the main https://adventuron.io/ website?

In the documentation for Tutorial A, section 24 reads Post-Mortum which should be Post-mortem.

Host

Noted, noted, noted.

Host

Fixed. Fixed. Fixed.

Submitted

Adventuron User Manual:

In match records the following symbols can be used to test for the following conditions

  •     ** Must include a value in this slot (verb or noun).
  •     - Must not include a value in this slot (verb or noun).
  •     _ May or may not include a value in this slot (verb or noun).

Looks like there's an extra "*" in there: ** Must include a value in this slot (verb or noun).

Submitted

It makes me think that match "_ _", which I use, doesn't make sense; match "* _" would seem more appropriate (it makes sense in PAW, but not here).

Submitted
** Must include a value in this slot (verb or noun).

Isn't there one '*' too many?

Host

Updated, will push to website with next release.

Host

Match _ _ actually acts like * _ as Adventuron will not process zero input.

Submitted (1 edit)

Which is the right opcode: win_game or end_game? The documentation talks about end_game, and Autocompletion proposes win_game.

Submitted

win_game plays a little tune. end_game doesn't.

end_game asks if you want to do a restore. win_game doesn't.

Submitted

Not for me, you don't! They work exactly the same way.

Submitted

Really? I just tried it. Are you using 8-bit mode? Maybe that affects sounds.

There are some attributes related to this to enable and disable sound and also to test whether sound is on or off. I used these in 'Igor's Quest'.

Submitted

Sure. I tried both modes again and got the same result.

start_at                 = my_location
locations {
   my_location : location "You are in a room." ;
}
on_command {
   : match "test -"  {
     : end_game ;
     # : win_game ;
   }
}
Host (1 edit)

In Adventuron

For games without jingles or rollback, all three options have the exact same function.

As far as adventuron is concerned,  end_game, and lose_game are the same (they will play the lose game "jingle" - when it is configured to be active), and offer a rollback option (if rollback is enabled). If rollback is rejected then it restarts the game.

win_game will play the win game "jingle" - when it is configured to be active, and will not offer a rollback option (the game is won).

end_game came first, and I really should have removed it. The problem is that the excalibur tutorial featured the command, so I use end_game as an alias for lose_game. 

In 8-Bit Compatibility Mode

As far as 8-bit compatibility goes, win_game, lose_game, and end_game are all the same (they generate an END opcode).

Submitted (1 edit)

In the documentation, Adventuron - Cookbook: 1.25. Disabling Dynamic Connection Scanning
In the second example, there are twice (at the beginning and at the end):

game_settings {
   # basic = only use connections table and do not use on_command table.
   exit_list_calculation = basic
}
Host

Thanks for the report.

Updated.

Submitted (1 edit)

In the documentation, Adventuron - Targetting 8-Bit Micros 3.9.4. Auto Redescribe mode (Beta):

For games that enable auto-describe mode, you need to call : success at the end of any code block that creates or destroys an object in the current location.
In 8-bit compatibility mode, adventuron will automatically refresh the screen when you use a : success command.

The term "success" and "sucess command" designates, I suppose, "Done;", but it's not very clear because you don't use this term elsewhere, and it doesn't refer to anything known in other Adventuron documentations.

Host

Added : success and : failure documentation in the command list section of documentation, with links to sample source code (in the cookbook section).

Submitted (1 edit)

Couldn't 'set_integer' be added to the Integer Operators table? Otherwise it would not appear in section: 2.12. Integers, of the documentation.

Host

I've made changes and they will be uploaded when the next release is made.