Inkpot - An container for Ink within the Unreal Engine developed by The Chinese Room.
This is a plugin for Unreal Engine 5.3 or later.
This is version 1.02.21 of the plugin.
Inkpot is a wrapper for the wonderful narrative scripting language Ink developed by Inkle Studios.
Fixed assertion when accessing variables that do not exist in the ink script.
Fixed relative path resolution bug that caused Ink source files to not import.
Improved compilation logging.
Added tag accessor methods to InkpotLine & InkpotChoice.
Inkplusplus port now matches version 21 of the Ink runtime engine, Ink version 1.1.1.
.net version updated to 5.0
Settings backed by CVars added.
First pass on auto reload and replay of ink source.
JSON serialisation now functional.
External functions are now implemented, along with functional tests.
Initial release.
Inkpot works with version 5.3 of Unreal.
Inkpot includes a C++ port of Ink-engine-runtime version 21, which can be found in the InkPlusPlus module.
InkleCate requires the .net framework 5.0 which you can download from here.
https://dotnet.microsoft.com/en-us/download/dotnet/thank-you/runtime-5.0.17-windows-x64-installer
(Without this you will not be able to import Ink source)
This plugin is distributed as source code which needs compiling.
You will need to install Visual Studio 2022.
https://visualstudio.microsoft.com/vs/
Make sure you have .Net framework 5.0 and Visual Studio 2022 installed.
In your project folder, create a folder named Plugins and copy the Inkpot plugin there.
Make sure the inkpot folder is called simply 'Inkpot'.
LIke this:
[Project Root Directory]/Plugins/Inkpot/
For an example of how this plugin should sit in your project see the InkpotDemo.
https://github.com/The-Chinese-Room/InkpotDemo
-
Inkpot is distributed as C++ source code and will need compiling.
Make sure you have Visual Studio 2022 installed. -
If you get this error VisualStudioUnsupported x64 must be installed in order to build this target.
For Unreal Engine 5.4, you need to be on v17.8 of the MSCV v143 toolchain. See here for more details.
https://forums.unrealengine.com/t/visualstudiounsupported-x64-must-be-installed-trying-to-update-a-project-from-5-3-2-to-5-4-1/1835116/5
-
Make sure you have .Net framework 5.0 installed.
Inkpot uses Inklecate to compile the Ink files and it needs .net 5.0.
Without this the Ink files will not import. -
Inkpot has only been tested as an application plugin and not an engine plugin.
It needs to be located in the project's plugins folder and not the engine plugin folder. -
The plugin folder name should be simply 'inkpot',
If you unzipped it directly to your project, it will likely be called 'inkpot-release'.
eg \plugins\inkpot -
See the inkpotdemo for how it should look in your project.
https://github.com/The-Chinese-Room/InkpotDemo
- Inky, the Ink script editor, will silently fail when saving to read only files.
Some version control systems will make the file read only when you check them out, eg perforce.
This can lead to some confusion when running Inky alongside Unreal & Inkpot.
Inkpot is made from three modules.
InkPlusPlus is the name of the module that contains the C++ port of the Ink Engine Runtime which can be found here
https://github.com/inkle/ink/tree/master/ink-engine-runtime
When porting the code from C# to C++ we came to the conclusion that we should keep the source as close to the original C# as possible to make updates easier.
This has now been updated to Inkversion 21, Ink v1.1.1.
A set of wrapper classes for InkPlusPlus to simplify Blueprint coding.
Manages the lifetime of the Ink story and provides the interface for Ink variable setting, getting and change notification.
This is the unreal editor facing part of Ink pot.
This manages the defintion of data types in Unreal for inkpot and the compilation of new Ink scripts as they are added to the project.
It also contains the unit tests for InkPlusPlus.
There area couple of supporting folders that make up the Inkpot distribution.
All the Unit tests for Ink.
Currently 180 tests.
This contains a copy of InkleCate and is used by the script importer to compile the scripts.
Inkle
for creating Ink. We've used this for much more than narrative.
UnrealInk
for giving us a good basis for creating InkPlusPlus.
Colin, Seb & Canute at TCR
for the brilliant job in porting the Ink Engine Runtime to C++, along with the editor asset handling, unit tests and Unreal integration, most of the work here in fact.