i've been wanting to code an engine for a point-and-click adventure for over 10 years (and have been trying it a lot of times), but i'm not quite sure how to handle the riddles. i've been coding a lot, but i didnt really learn it, so it's mostly self-taught and i dont see if i'm doing something horribly wrong in my concept.
this is where i need help, opinions and hints: can it work? do i oversee anything that might 'break my neck' after 50 pages of code, like 'duh, i should have thought of that from the start... now i can do it all over.'
this is my usual approach (i've done it in visual basic 6 most of the time):
objects have a parameter called "action" (or such), which means if the user clicks on them, the action is done. there are (for example) "GoToScreen #xxx" or "show LookAtObject-text" or "take Object" (if its takeable). the objects have "triggers" (i'd rather called them Events, but i didnt think of that at the time), which can change properties of objects (see below) or simply show texts or so.
a example would be: opening "Door #xxx" wont work (object-action "GoToScreen #xxx" is disabled), but picking up a key calls the Event "set Door #1 GoToScreen True".
i have a real problem thinking of anything that wont work if i code it in this fashion, but i also think the adventure-genre is very old and there is a perfect "recipe" doing the riddle-system. i have searched to much for something like this, but never found anything.
i would very much appreciate anything anyone has to say to my problems, thanks in advance!