fCraft's source code repository is located at http://svn.fcraft.net:8080/svn/fcraft/. You can access it by a shortcut url: svn.fcraft.net. To download a snapshot of fCraft's source code, you can either use an SVN client (like TortoiseSVN), or use "Download Tarball" feature at websvn.fcraft.net.
What are the different build configurations?
- Release (recommended, default): For normal use. Produces the most optimized copy of fCraft, and intercepts any unhandled exceptions.
- Debug: For debugging. Disables some optimizations. Runs additional self-tests. Does not catch unhandled exceptions (crashes).
- Debug_Events: For debugging events. Just like Debug, plus every raised event is logged.
- Debug_IRC: For debugging IRC bot. Just like Debug, plus all IRC input and output is logged.
- Debug_Scheduler: For debugging the built-in task scheduler. Just like Debug, plus all Scheduler activity is logged, and /TaskDebug command is enabled.
Binaries are not included on SVN, you will need to build it. To build a copy of fCraft, you will need Microsoft VisualC# 2010 Express (free), Microsoft Visual Studio 2010, or MonoDevelop (free, unsupported). Make sure to select the correct build configuration before building. Binaries will be copied to the /bin/ folder in the branch directory.
What are the different "branches" on SVN?
Each branch contains a different snapshot of fCraft's code. Branches are:
- /tags/ - Code snapshots corresponding to stable fCraft releases. This is the version that you should use for any mods.
- /branch-0.10x/ - First ever version of fCraft. Does not work. Not updated.
- /branch-0.33x/ - Oldest version of fCraft that still works. Last version without multiworld. No longer updated.
- /branch-0.53x/ - Previous version of fCraft. No longer updated.
- /branch-0.60x/ - Current version of fCraft (trunk). Frequently updated. May contain unstable code.
- /branch-0.64x-abandoned/ - Abandoned experimental branch. Contains some unstable/untested code.
- /branch-0.70x-abandoned/ - Abandoned experimental branch. Thoroughly unstable.
- /branch-0.90x/ - Future version of fCraft. Under heavy development.
See fCraft.net/api for an API reference. If you are referencing fCraft.dll from your project, make sure to include fCraft.XML file, which will allow VisualStudio to show inline help. For a general overview of fCraft structure, see Architecture article on the fCraft Wiki. For specific examples, see Mod Examples article.
I am using fCraft.dll. How do I get Intellisense to work with it in VisualStudio?
When you build fCraft.dll from source, an XML documentation file will be generated (fCraft.XML). Copy that file together with fCraft.dll into your project folder to get Intellisense working.
Will a plugin system be added to fCraft?
Yes. A system of binary plugins is planned for fCraft. You will be able to create redistributable plugins (as .dll files) in any .NET language: C#, VisualBasic, IronPython, etc. This feature is scheduled for next major release (0.900).
Will scripting be added to fCraft (e.g. Lua scripts)?
No.
I don't know anything about programming. Can I still mod fCraft?
No.