Suggestion: hold "key" to cap siege weapon

noobs wouldn't figure it out

 

More buttons = not likely. Could make it require sitting in it but you cant guard it with 1 person then.

The ballistae aren't meant to spawn more people when they're being capped but its a long standing bug. Spawn system is a mess.

 

Re: cap defense - I honestly couldn't remember if you could break the cap with more people - turns out you cant. Could be a reasonable change if there was some sort of display for it.

Re: no spawn protection at ballistae - honestly that'd just make them even more frustrating for both teams.

Re: kag 2 - There might. We've definitely talked about it. We're just (MM and I, not the interns afaik) feeling pretty done with the game at the moment - TR is much more enjoyable to work on because though it's still got the same old engine problems, the game code is reasonably clean. A rewrite of "kag 1" will never happen, been there, not interested in that ride again. Sorry to be frank, haha.

 

Re: a rewrite - there's not enough financial stimulus for us to ever attempt it. Re-launching the game on steam isn't possible.

Re: KAG2 - I dont want to talk about it much as there is nothing beyond a few conversations between MM and myself at the moment, but the attraction is being able to completely change whatever we like. The current progression systems are broken, but there are lots of players who have learned them and rely on them. The current class balance has a lot of overlaps and situational patches, but a lot of players have spent a lot of time learning them. The current movement makes building (particularly front line building) quite a difficult task, but every player depends on those mechanics. Building itself has tens of flaws, but again every single builder has learned to work with them - small changes are possible, but still garner anger, and at the end of the day big, widesweeping changes would be needed to fix it.

Everything we changed from classic->KAG was complained about in some form or another and it really drives a wedge into the community. We'd be happy in future to do something that's an abject sequel to allow us to take it in a different direction. While I'm sure changes would still garner complaints, they're more expected by people with a sequel, and we wouldn't be taking anything away from anyone by changing the game they've already paid for and already enjoy (again, something that the classic diehards have always perceived us as doing).

We'd also be free to change the aesthetic, what classes were available, the pacing, goal, etc etc for the game. That level of creative freedom with the design is honestly the only thing that's attractive about the idea of more work on KAG.

I wont be talking more about it in this thread, as it's a huge derail. Know that it's possible, the motivation is obviously HUGE CHANGES BREAKING YOUR FAVOURITE CLASS INTO SMITHEREENS, and if it happens it'll be in a long time.

Re: TR requiring rewriting engine - we're sharing the engine between KAG and TR - its a double edged sword as it means anything that TR breaks in KAG needs to be fixed and reconciled, and there's more testing to be done on both sides, but it also means anything we do that makes more possible with the scripting engine comes over to KAG to be used in mods as well - most notably all the tilemap stuff that happened a few months ago.