Trust me, I saw lots of things which didn't make sense.... some of them were mine lol
Nice. Now a serious suggestion: if you want to get anywhere with this SDK, there are 2 things which are a must imo:
1 - Auto-update/auto-patcher;
2 - Web support (API).
In short, the SDK is looking great in each update, but for someone to start developing more seriously on this I think you need to give the final user the possibility to auto-patch the SDK with a single click, and the final game itself as well (since this SDK is best used in TCs and not simple online/offline mods, it would be cool to have the essential features a game nowadays has: if the developer makes a patch, the game auto-patches, if the developer has news, then the launcher or the game should show these news).
Also web support is a must: building an API to communicate with a web server, using JSON perhaps, can lead the game to save stuff remotely in a database, and also retrieve. Think for example online authentication or any game with RPG elements.
I say this because honestly I am not seeing anyone even using the SDK for just mods or other stuff which aren't worth the trouble for the amount of active players, but Total Conversions (aka new games) would make a lot more sense and without all the complexity AND hardware requirements other SDK's have (*cough* UDK *cough*).
Also, make the web requests latent functions (for some reason Epic thought that they could make a HTTP request to a web server in a single game tick...), since they can take long or not getting a response at all and time out, thus being preferable to be a latent function so the game does not freeze while doing this.