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. 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: Why does Mapbase put everything 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.