> Agent-readable docs index: /llms.txt. Download /docs.zip to grep all markdown files locally.

---
title: Getting Started
description: "From zero to a running extension: unlock Developer mode, create an extension, write your first script, and publish it."
icon: rocket
sidebar_position: 2
---

# Getting Started

This page takes you from zero to your first running extension. No prior
experience with Neverlose scripting is needed. Account, cheat menu, and market
steps are covered in detail in the Product tab; this page links to them where
you need them.

## 1. Unlock Developer mode

To develop local CS2 extensions, you need active Developer mode and a
Neverlose CS2 subscription. After buying Developer mode, restart the cheat.
See [Developer Mode](/cs2/product/developers/developer-mode) for pricing,
renewal, and access rules.

<Card title="Developer Mode" icon="lock-open" href="/cs2/product/developers/developer-mode" arrow>
  Annual access, renewal, and how it relates to your product subscription.
</Card>

## 2. Create an extension

<Steps>
  <Step title="Open Manage Extensions" icon="package">
    A **Developer** section is now at the top: these are your own extensions.
  </Step>

  <Step title="Create the extension" icon="folder-plus">
    Press **Create new developer extension** and give it a name. Scripts and
    libraries are created the same way.
  </Step>

  <Step title="Open its folder" icon="folder-open">
    Use **Open Folder** from the extension's **…** menu and open the folder in
    your editor. To get autocompletion and hover docs for the API there, see
    [Editor Setup](/cs2/api_reference/introduction/editor-setup).
  </Step>
</Steps>

<Frame caption="Your extensions under Developer, downloaded ones under Market">
  <Image src="/images/cs2/developers/manage-extensions.webp?v=674e6c0b" alt="Manage Extensions with the menu of a developer extension open" width="1927" height="1375" placeholder="data:image/webp;base64,UklGRoQAAABXRUJQVlA4WAoAAAAQAAAADwAACgAAQUxQSDkAAAABYBPbVqMnABeowAM1eKGmxAGSchSBAbbcjuAgIiaA220F6H87PhuUHHxVHiwnDqZhBxF4x+22AgAAVlA4ICQAAABQAQCdASoQAAsAAsBMJZwABAAAAP71wDZ7oOULMatHL6BIYAA=" />
</Frame>

## 3. Write your first script

Put this in `main.lua` and save. Enable the extension in **Manage Extensions**,
return to the game, and open the Neverlose menu. When the extension loads,
the text appears in the top-left corner:

```lua main.lua luaintelligence=true semantic="lua:cs2:cs2/api_reference/introduction/getting-started:0:dad41b336484"
local font = render.LoadFont(render.EspFont.kBold)

events.render(function()
    render.DrawText(Vector2D(20, 20), Color(255, 255, 255), font, nil, "Hello from my extension")
end)
```

`main.lua` runs once each time the extension loads, and `events.render` calls
your function every frame. [Lifecycle and Events](/cs2/api_reference/extensions/lifecycle-and-events)
explains what runs when, and [Anatomy](/cs2/api_reference/extensions/anatomy)
covers the other files an extension can have.

After editing, save your changes, return to the game, and open the menu.
See [Manage Extensions](/cs2/product/developers/manage-extensions#check-changes-in-the-game)
for reload conditions.

## 4. Use libraries

To build on a market library, a built-in module such as `ffi`, or another of
your own extensions, add it to **Requirements** in the extension's settings and
load it with `require`:

```lua main.lua
local ffi = require("ffi")
```

<Card title="Requirements" icon="puzzle" href="/cs2/api_reference/extensions/requirements" arrow>
  Native, market, and local modules, and splitting your code across files.
</Card>

## 5. Publish on the market

When the extension is ready, create a market item, upload a build from
**Manage Extensions**, then use the **Update** action on the market item page
to submit it for review. Uploading alone does not submit the build.
Publishing and updating CS2 extensions requires active Developer mode,
including for free items. A library is published the same way, as an item
marked **Make it a library**.

<Columns cols={2}>
  <Card title="Publishing on the Market" icon="store" href="/cs2/product/developers/publishing" arrow>
    Create the item, upload builds, pass moderation, and set the price.
  </Card>

  <Card title="Manage Extensions" icon="package" href="/cs2/product/developers/manage-extensions" arrow>
    The extension menu, settings, requirements, and snapshots.
  </Card>
</Columns>

## Next steps

<CardGroup cols={2}>
  <Card title="Lua Crash Course" icon="graduation-cap" href="/cs2/api_reference/tutorials/lua-crash-course" arrow>
    The parts of Lua you need for extensions, from tables to closures.
  </Card>

  <Card title="Reading API Pages" icon="book-open" href="/cs2/api_reference/introduction/reading-these-docs" arrow>
    How to read signatures, overloads, and types on the reference pages.
  </Card>
</CardGroup>
