Skip to content

Welcome to the Experiment Developer Portal🔗

This wiki documents the Lua bindings to the Source Engine (Source SDK 2013) in Experiment. With this wiki we aim to provide reference material for the Lua API, as well as tutorials and examples to help you get started with Lua scripting in Experiment.

With Experiment we aim to help you quickly prototype Source Engine mods without having to write any C++ code.

First Steps🔗

Depending on your experience we recommend the following steps to get familiar with the Experiment Lua API:

For Beginners   |  ⌚ 1-2 hours

Experience Required: Minimal scripting experience

  1. Follow The Basics (tutorial)

    This will guide you through the basics of Lua scripting in Experiment by creating:

    • A simple script that launches all players into the air on command.
    • Converting that script into a reusable function.
    • Adding parameters to the function and command to control the launch height.
    • Converting the script into an addon that can be shared with others.

  2. Read up on the Concepts in the Experiment Lua API

    Learn how hooks, classes, libraries and more can help you create more complex mods. It contains some examples that can help you understand how to use these concepts.

  3. Save yourself and your fellow developers time by reading the Best Practices

    Learn how to write clean, efficient and maintainable Lua code. Additionally this shows you how to deduce which functions can help you achieve your goals.

For Intermediate Users   |  ⌚ 1 hour

Experience Required: Basic Lua scripting experience

  1. Read up on the Concepts in the Experiment Lua API

    Learn how hooks, classes, libraries and more can help you create more complex mods. It contains some examples that can help you understand how to use these concepts.

  2. Save yourself and your fellow developers time by reading the Best Practices

    Learn how to write clean, efficient and maintainable Lua code. Additionally this shows you how to deduce which functions can help you achieve your goals.

  3. Head over to the API References: