State of the beta

i hope they will fix that archers moves running like a girl whos gonna to be raped by a Dynasaur is ugly now

 

Many many many thanks This is the status update i needed and it's awesome! I agree TOTALLY on many aspects of this post, like the farming and canopy issues, and now i'm sure more than ever that Kag 1.0 will be MY Kag! Many thanks!

 

Running like a girl? Running like a 1337 ninja bawss pro... or whatever you kids might call it nowadays.

 

Girls are sexy and have boobies :3 I prefer them over "dynasaurs" that are fat.

 

This project's scope just keeps expanding with no clear end goal. Meanwhile testing involves a select group of arrogant KAG guards that suck the dev's dick--the dev isn't creatively challenged. I have no idea where this game is going. When it's released I hope it resembles original KAG, but I fear it won't. The game isn't about building castles anymore, it's about attacking them. The game isn't about team work anymore, it's about "fun."

Don't give me a bullshit reply like "well that's what modding is for" that's the same awful reply as "well if you don't like it go make your own game." No one will play on modded servers. It's all about vanilla.

 

"We want the game to be dynamic and focus more on attacking than defending."

Sounds like it's going to end up like the clan matches where players rely on 5 tile high walls to defend. How many testers does the game have even? And yes I'm going to still go with you guys aren't creatively challenged. The groupthink among the high tier KAG community was obvious in every gold server.

 

You and Geti are epic :) And makes epic game :) But why we cant play Test version like when you was making firstworkshops? :)

 

You said that you had all the stuff that was on that chart made and in game. Why not release a build so that we, as a community who was promised those features, at least get to test and try them out on a larger scale? I find it disappointing that you are making shifts to the game for what you feel it should be, not what your community may or may not want it to be.

This used to be a game about defending your castle from people trying to steal your gold, and it sounds like you are just making it a game centered around attacking. You already lost a ton of old KAG players when you took too long developing zombie mode, and I fear that you'll lose the last of us when you make a mode that targets a different objective than the one you initially promised.

 

saw was MM and liked it before reading it at all XD
i could forsee battering rams working like melee catapult with a loading bar and more health and can be damaged by swords. battering rams could look like this:

Spoiler: Spoiler Hint

rather then the hand holding one

 

So, who was posting lies about "future content" in the Facebook and Blog? please, fire that guy or admit you just tried to hook people to buy the game with all that stuff.

It always felt like that, small screenshots with no information, no comments from the guy sharing that for WEEKS, the videos, everything.

I understand you can't do that now, but there are just too many things that are "already done but can't release now" and then "oh it didn't work after all, sorry".

 

Whilst a lot of you think that public testing would be great but in reality it is just lots of people creating identical threads, requesting unrealistic features and have little knowledge of what it means to make these features. The Devs would have to spend a lot time looking through everything explaining why that is happening, how to get it working, why that idea won't work, organise testing for the public and answer questions on new changes. At the moment the Devs aren't necessarily there when we test and we are quite diverse testers and all have different opinions and we are hardly 'sucking the Devs dicks'; Geti lives in Australia and MM in Poland think through the logic!

Different thing slightly but still applies:
Personally, I do not respond to individual support requests or personal messages (with a few rareexceptions). Why, you ask? Wouldn't that help develop community? Doesn't ignoring it hurt the product? Well, actually, the truth might be startling: no. Not at all. Let's look at a graph:

This graph shows a hypothetical (and somewhat realistic) scenario in which I decide to take in support requests. A low estimate of the number of emails/PMs I get a day is 2 new ones per day (it's more like 3-5). I also assume (again, a low estimate) that each response takes 30 minutes of work. This scenario assumes that I respond - and we also assume that persists the communication and support, since I'd have to respond to their response, and so forth. So the first day, I've got one request. 30 minutes gone from my development time that day. Not bad. But see what happens to my free time as I add more responses? The amount of time I get to actually fixing the product decreases exponentially. By Day 5 I'm barely even coding or documenting anymore.

 

Studios I believe you do not understand the main focus of the closed beta. The original KAG's coding was flawed; with each addition of new features the team would run the risk of detrimentally changing core gameplay in ways that made combat unenjoyable. As shown by Geti's statement the main focus on the closed beta test was to create an engine that allowed the addition of new features without detracting from the core gameplay.

While you are right that a smaller test group will limit feedback, the mob mentality of many KAG consumers and the scathing vitriol of many commenters did not offer constructive criticism as to what exactly was wrong. Thus the team made the decision to make the tests a closed beta. While you question the integrity of the testers, many members of the test group challenge (to the point of extreme arguments) the developers with each decision implemented in order to make sure that each design decision is not a mistake. All of the volunteer testers set out for this goal (or one very similar to it), "Clearly defining what gameplay made the original KAG fun and cementing that gameplay so that future additions would not detract from it."

 

Couple of questions:
1. how much information will be released on the game prior to the launch of the beta?
2. how is bomb jumping now?
3. Regarding the matter of the testers, when was the last one added?
4. Are you going to let some non-testers to scout out the game prior to launch?

 

The Knight for example, is the best Unit so far, in most games he doesn't really needs the Archer or the Builder, it is the most satisfactory class to play, best mobility, best attacks, and they just keep adding more to the Knight from time to time.

IMO they should not be able to use bombs, and if another unit gets to use the bomb, that unit should not get a Shield, I hate the bomb jump, sure it is fun, but too overpowered for the Builders and Archers.

 

That's what I fear, that the best team will just be all knights with a few siege equipments. Taking bomb from them would be a good idea.

Dude you can't assume we are all on the forums 24/7.