Loner-StrikeReference

Reference

Sharing

What travels with a mode, what players need, and how credits work.

Share a mode or map from Tools › Community › Publish. The app makes the package and fills in the credits; you upload it to GameBanana yourself, and it shows up in everyone's Community tab. The app never uploads or signs in to GameBanana for you.

What travels with a mode

Only the graph is shared. Each player's app builds the plugin from it on their own computer, so nothing that runs code travels. With it go:

  • The models, sounds and sprites it uses that aren't the game's own, wherever it names them: node settings, file variables' start values and data table cells (a custom .spr for Objective Marker, a model for Spawn Prop).
  • The custom creatures it spawns with Spawn Creature, with their models and sounds.
  • The models and sounds of its NPCs (Spawn NPC).
  • Its data tables, map markers, Timelines, functions and macros (they're part of the graph).

Every file has to be on your computer, or linked to the GameBanana item that has it: see My mode › Details › Requirements. Starter library items you added are copied into your mode, so they travel too; your own My library items don't go to Community on their own yet.

What travels with a map

  • The map, its nav and map knowledge (so bots play it), a fresh download list and the overview.
  • Its own sounds, models, sprites and textures; never the game's own.
  • The custom creatures its spawners use, and its NPCs' models.
  • If you tick it, the editable source (below).

Never shared: the game's own files, plugins and compiled code (.amxx, .sma, .dll, .exe, scripts), settings files (.cfg, liblist.gam, plugin lists), archives inside the package, and the Metamod and dlls folders.

Creatures and NPC models in your own folder

Custom creatures and NPC models are carried in your own folder, named for your GameBanana account, so they never clash with anyone else's. Players see them as "crawler by you". Publish lists them ("Includes: crawler (with its model)").

On a player's computer, shared creatures go into their own marked block in creatures.ini; their own types are never touched. Removing the mode or map removes only that block, and a type two installs share stays until both are gone.

Publish it

  1. For a mode: make sure it compiles and run a Test run. For a map: compile it into your game.
  2. In Tools › Community › Publish, pick A game mode or A map. The app says what's missing.
  3. Fill in Name, Made by (your GameBanana name), About it and screenshots. For a mode, set How well bots play it; the Studio may suggest one.
  4. Check Credits for the files it uses (below), and the AI box.
  5. Make the package, then open GameBanana and sign in there.
  6. Upload the package unchanged in the Counter-Strike 1.6 section, with the screenshots.
  7. On GameBanana's Technical tab, under Tags, add a Custom Tag with the value LonerStrike (the title can stay empty), press + and save. That's how Community finds it.
  8. Paste the credits into GameBanana's Authors section. The app has a copy button for it.
  9. Once GameBanana has checked the file, paste the page's link in the app and press Add to Community.

Most things are listed within a few minutes; some go to a moderator first. If one is turned down, the app says why.

Power tools get a badge

A mode that uses Run Server Command, Run AMX Command, Kick or Call Plugin Function shows a badge for each on its Community page, and players confirm before installing. Those nodes only run commands that change the game, both when the mode is built and as it runs. If you can do it with other nodes, do: fewer badges, more players.

Credits

Loner-Strike tracks where every file came from. Credits lists each file's source, makers and what its page allows. When a page wants you to ask first, ask the maker, then press Permission granted… and note who, where and when. A file whose page doesn't allow sharing stops the package until you record permission; Add credit… names the maker of a file the app doesn't know.

The credits go into the package's README.txt, the Community listing, and a block for GameBanana's Authors section: you, the maker of the original when it's a remix, the makers of shared creatures it carries, and the makers of the files it uses.

Map source and Remix

When you publish a map, tick Include the editable source and pick its project. The package gets a source/ folder: the map editor's project (.lsmap), a Valve 220 .map that TrenchBroom, Hammer and J.A.C.K. open, a texture file with only the map's own textures, and a short note. Players who only play it never get source/ in their game.

On a map shared with its source, Remix this map saves a copy as a new project of yours and opens it in the map editor. A mode can always be remixed: Remix in Game Mode Studio makes a new mode of yours. Either way, when you publish the remix, it says "A remix of" the original, by its maker. Only the first uploader can update a creation; everyone else posts a remix that credits it.

Updates and Go back

To update something you shared, upload the new file to its GameBanana page, then paste the link in Publish again. Players get it as an update, with your notes:

  • Never while it's in use: the map or mode being played updates at the next map change. Servers update once nobody's playing it there.
  • Go back to the previous version restores the old one; a failed update does it by itself.
  • Placed prefabs and remixed modes don't change.

The Published tab lists what you've shared. Unlist takes one off Community (installed copies stay); List again puts it back.

Plugin Studio stays local

Community never takes plugins or compiled code. A plugin from Plugin Studio stays on your computer: to share one, Export… its .sma and post it on GameBanana or AlliedModders yourself. To share a mode through Community, make it in Game Mode Studio.

See also

A hand-written guide. Every node it names links to the node reference, which is made from the app's own catalog.