Sprint 3 Review

[Wyqer]

General Information about sprint reviews
As we will release a working iteration of the new framework after every sprint, everyone is invited to help with testing the sprint results.
The only thing to remember is that you should only report bugs in this issue, which are caused by the contents of this sprint (which are listed below). So it is vital to look at the content description to see what was actually added. Only by reading this you know what we've really intended to implement and defined as done.
I guess you understand that reporting things which weren't even planned to be part of the sprint won't help in any way.
This releases (which are also marked as Pre-release) aren't meant to be played as replacement for the current framework. It is for testing purpose or a kind of first look at features/changes which will be part of the 0.97 release in some months.

Summary of this sprint
The UI defines overhaul is basically finished. We've established basic classes and some special case child classes like the title bar or content area. Also some defines for 3 general UI positions/sizes (standard, large and for "upper left corner"). The current set of the design is identical to the A3 UI, which will give the Liberation dialogs a much more native feeling. It also adapts to the individual userside A3 settings concerning colors etc.
We've also started with the build module and already implemented a first draft for the new building system, which will work via a floating cam to build the FOB buildings. No more "running around with a green thing in front of you", now you can really have a look from all directions if that H-Barrier is exactly where it should be. It's already working for testing, means that you can place buildings from the build menu. Currently a blue arrow shows you where it'll be placed. During the next sprints we'll implement a preview of the object (a green thing again I guess) and the ability to rotate and lower/raise the object.
There is also a small "failsafe" mechanism implemented for errors in user edited presets or config files. If you've a syntax error somewhere the mission will directly end with a hint about this circumstance. This way we can ensure that players won't get weird side effects due to mistakes in edited files. This is a good hint for the admin/player and we can be sure that the reported error isn't connected to a bad edit.

We'll now have a break for about 3 weeks. Name it "summer vacation", if you like.
So the next development sprint will start July 23rd and will last 2 weeks.
Until the start of the sprint we'll evaluate possible contents for that sprint, think about their respective story point values and plan what we'll be able to achieve during the 2 weeks. You're always invited to state your opinions on the issues we create to keep the development as transparent as possible.

Content of this sprint

Task	Description	PR
#425	Bugunt for Sprint 2	no direct PR
#415	Free camera view for building	#441
#426	UI defines overhaul	#440
#428	Redesign of spawn dialog	#442
#430	Preset file syntax error detection	#435

Released sprint result
https://github.com/KillahPotatoes/KP-Liberation/releases/tag/v0.97S3

Bugs found so far

Related Task	Description	Reported by
Nothing	found	so far

Sprint History

Sprint	Quick Summary	Details
2	Event handling and action manager	#427
1	Basic CTI functionality: Intro, Spawn, FOB deploy, capture sector, win campaign	#404