Frequently Asked Questions (FAQ)

---

Q: Does Mapbase modify Hammer?

A: Mapbase does not directly modify Hammer. It runs as its own mod or part of another mod with Hammer configured to use that mod's files and directories. Mapbase improves the FGDs based on existing framework and does some extra shader stuff which can be seen in Hammer, but it doesn't actually change the editor itself.

---

Q: How can I see what's changed in Mapbase?

A: The most detailed list of changes is Mapbase's Trello board, which was used during development to keep track of changes, although it has been falling behind on content introduced in recent updates. There's also the Entity List, which shows every single entity available in Source 2013 and Mapbase, showing how existing entities have changed and listing entities introduced by Mapbase.

---

Q: Will support for other games be added to Mapbase in the future? Can I use Mapbase in my mod/game that does not use the SDK's HL2 code?

A: Mapbase was designed to be used in Half-Life 2 mods running on Source SDK Base 2013, but it was also designed to function in more than just Half-Life 2. The upcoming MP port will allow Mapbase to be used in Source 2013 MP/Half-Life 2: Deathmatch mods. People could port it to other games themselves, but there are currently no plans for officially implementing Mapbase on any other branch of Source.

---

Q: Does Mapbase use content from leaks?

A: Mapbase does not use any content taken directly from Source-related leaks, and it never will.

Q: Where does Mapbase's VScript library come from? Does it use leaked code?

A: Mapbase uses a custom implementation of VScript in Source 2013, created from scratch using the public Squirrel API and the Alien Swarm SDK as a reference for Valve's library. It was created by reductor in an extensive effort to bring VScript to Source 2013 and its users. It does not contain any leaked code. They also have important structural differences, like Mapbase's introduction of enums/constants and the fact reductor's library is a static library (.lib), not a dynamic library (.dll).

Q: Where do Tony Sergi's changes come from? Are they using leaked code?

A: Tony Sergi's changes were from the Source 2007 SDK on Steam. They're not in the Source 2013 SDK because Valve did not branch off of the Source 2007 SDK when they created the new codebase, so it did not contain Tony's changes by default. They do not contain any leaked code.

---

Q: Why does Mapbase usually put everything in an update into one commit for every update instead of putting changes into individual commits?

A: The logic behind this is that deriving projects won't be cluttered with Mapbase commits, seeing their own commits more than that of Mapbase's. However, contributions are excepted from this rule for the sake of preserving history and crediting contributors for their contributions.

---

Q: Is Mapbase slower than regular Source 2013?

A: Not really. No specific and thorough comparison of FPS in between Mapbase and vanilla Source 2013 has been given, but Mapbase's changes don't usually precipitate regular performance problems.

If you have major performance problems after merging Mapbase into your mod and/or you have made a specific and thorough comparison of the FPS in between Mapbase and vanilla Source 2013, please contact me immediately.

---

Q: What's the difference between Mapbase and Source 2013: Community Edition?

A: Source 2013: Community Edition basically aims to be what Valve's repository would be like if Valve continued to accept pull requests. It integrates common fixes from all over the community as a repository made "by the community, for the community" in a clean, lightweight package.

Mapbase has similar goals. It aims to make common fixes from all over the community more accessible to mappers who don't know how to code. Contributions are also encouraged and highly valued. However, these goals are part of a different overall mission: To make it easier and less frustrating to create maps and mods for Source 2013. Mapbase adds new features like additional logic entities, I/O/KV, etc. and is generally more geared for allowing mappers to do things only programmers would normally be able to do. The kinds of things Mapbase adds are out of the scope of Source 2013: Community Edition, which rarely adds new features.

Source 2013: Community Edition was not made out of any hostility towards Mapbase. In fact, Mapbase will most likely be drawing code from its repo in the future.