Maximus BBS

Documentation for Maximus BBS — Next Generation

View on GitHub

Learning MEX

A hands-on, story-driven guide to MEX scripting

It’s 2 AM. Your Board Is Running. Let’s Make It Weird.

You know how to compile a script. You’ve seen “Hello, world” land on a terminal. Congratulations — you’ve done the thing every programming guide makes you do first, and it was exactly as thrilling as printing two words to a screen ever is.

Now let’s do something real.

This is a ten-lesson journey from “I sort of know what MEX is” to “I have a working game on my board and my callers think I’m a wizard.” Each lesson builds on the one before it. Each one makes something you can actually use. And each one happens the way the best BBS hacking always happens — late at night, one idea at a time, fueled by curiosity and the faint glow of a terminal.

You don’t need prior programming experience. You don’t need to read the Language Guide first (though it’s there when you want the fine print). You just need a board, a text editor, and the willingness to try things and see what breaks.


The Roadmap

Here’s where we’re going. Each lesson is self-contained enough to stop after, but they’re better together — by the end, the skills stack up into something genuinely cool.

The Basics (Lessons 1–3)

You’ll go from printing text to having a real conversation with your callers — and knowing exactly who you’re talking to.

Making Things Interesting (Lessons 4–6)

Your scripts learn to think, repeat, and remember.

Building Real Things (Lessons 7–9)

Now you’re building features your callers will actually notice.

The Grand Finale (Lesson 10)

Everything comes together.


How to Use This Guide

Go in order if you’re new. Each lesson assumes you’ve done the ones before it.

Skip around if you already know some programming. The lessons are self-contained enough that you can jump to the topic you need — but if something doesn’t make sense, the earlier lesson probably covers it.

Type the code yourself. Seriously. Copy-paste teaches your clipboard, not your brain. The examples are short on purpose.

Break things on purpose. Change a variable name. Remove a semicolon. See what the compiler says. The error messages are pretty good, and understanding them is half the skill.

When you want the deep reference — every function signature, every type rule, every edge case — the Language Guide and Standard Intrinsics are waiting. But you don’t need them yet.

You just need Lesson 1 and a late night.

Let’s go →