I have just uploaded three files. One of them is an ATM machine,
another is a library, and the third is a test program to show the
merits of said library.

About the ATM machine:
I hadn't found any free ATM programs out there, so I decided to learn
MUF so I could make one.
This was my first program, and I put it through a few revisions before
I decided it was ready.
Interesting features:
Account. You can withdraw and deposit pennies from the ATM. Likewise,
you can get a balance.
Interest. Pennies in the ATM earn interest! You can change the interest
figures as desired by changing some of the $defs

About the Library: lib-quest

Lib-Quest is a quest-management library. It stores quests for players
in a to-do list to be accessed by the command @quests.
New quests can be made using @newquest, which will store the quest on
an object. Then, from a program, you can use the library function
QuestAssign to assign the quest to a player.
Several quest manipulation tools can be found in the library.
QuestIncrememnt will add to a player's progress, QuestDecrement will
subtract from it.

QuestSet will set it at a certain Value, And
QuestReset will put it back to the value it was when first assigned.
Quests can also be hidden. Hidden quests could be useful for ester
eggs or whatever background quests that don't really need to be displayed.

Each quest also has a QData folder, where you can put values you need
to customize the experience and that can be cleared when you reset the
quest. If you don't want them to be reset, put them in a folder of
your own creation inside the Quests working Directory.
Some public variables like the quest's working directory,
number, etc are set by using the ShortParse function. It's useful to
run that function before doing much else in your program.

The testprogram, quest-braineater, demonstrates how the program can be
used. It's a simple example, but proves the point well enough, I
think. This program is in the file quest-example, which is filled with
instructions from which to recreate the test environment the program
ran in.

One last thing: I am almost entirely self-taught. The extent of me
being tutored is the past few posts I made here and fEk from Altered
Realities MUCK telling me about the sysparm primitive.

As such, I have no real way of judging how clever my programs are in
comparison to norm, or how well they are written. Since I've had no
tutor aside from what I've read in a couple of places online, I
probably am lacking some basic tricks, shortcuts, etc that would make
my life easier and my code cleaner. If you have any tips, I am a
gracious, willing learner! Please help! Thanks.

As far as I know, the programs are bug-free. I've tested them, but
there's only so much a man and a couple of his friends trying out his
programs can test for. Any feedback/bug reports/feature suggestions
are greatly desired. Thank you very much, and I hope you enjoy these
programs!