Todays updates - 16 September 2016

[Simon]

That kbd head update is gr8

ikr!

it's not like people charge up their dfs whenever they fight dragons which is it's only purpose

!!!

Uncharged DFS has the same stats as a mith kite...

Ur bad kishan

[Amount]

That kbd head update is gr8

ikr!

it's not like people charge up their dfs whenever they fight dragons which is it's only purpose

!!!

> People asked Mike to do it.
> Mike delivered.
> 'Pointless update'.

[Azu rite]

That kbd head update is gr8

ikr!

it's not like people charge up their dfs whenever they fight dragons which is it's only purpose

!!!

> People asked Mike to do it.
> Mike delivered.
> 'Pointless update'.

Pkhonor logic

[Iron midas]

Cool updates

[Rwter]

That kbd head update is gr8

ikr!

it's not like people charge up their dfs whenever they fight dragons which is it's only purpose

!!!

Uncharged DFS has the same stats as a mith kite...

Ur bad kishan

to get a kbd head, people must fight kbd
which they will be doing with a dfs
which charges it up
so no mith kite

pkers won't really use it either for the most part since most of them don't even know what a kbd head is

but if it makes everyone happy then why not great update XD

[Ruler]

kishan its just a little QoL. Its not like it took him hours to code that...

[Rwter]

kishan its just a little QoL. Its not like it took him hours to code that...

benefits a total of 10 people, max, when we've been suggesting small pking qols all month without anything.

[Ruler]

kishan its just a little QoL. Its not like it took him hours to code that...

benefits a total of 10 people, max, when we've been suggesting small pking qols all month without anything.

small QoL updates are always nice. They barely take time to code and as the name says, these are just little additions to improve the gameplay. The problem isn't that he added this QoL, the problem is that he doesn't add small pking QoLs, so stop whining about this one.

[Rwter]

kishan its just a little QoL. Its not like it took him hours to code that...

benefits a total of 10 people, max, when we've been suggesting small pking qols all month without anything.

small QoL updates are always nice. They barely take time to code and as the name says, these are just little additions to improve the gameplay. The problem isn't that he added this QoL, the problem is that he doesn't add small pking QoLs, so stop whining about this one.

not whining about the update, just the fact that no one will use it and mike prioritises it over urgent pvp changes.

[Rapsey]

benefits a total of 10 people, max, when we've been suggesting small pking qols all month without anything.

not whining about the update, just the fact that no one will use it and mike prioritises it over urgent pvp changes.

These changes (the KBD head, frost dragon tasks, barrelchests ladder etc) are all things we can do in 5-15 minutes each total. This makes them ideal to do now as it allows us to release an update without having to put the work on the new client on hold. This particular update was mostly about the fixes to the database connections. This was something we wanted to release ASAP as it does solve some critical issues behind the scenes. We just added a few small improvements so there wouldn't be a server restart seemingly for nothing.

These changes require very little time to implement because:

- No one is opposed to them, so we don't have to go out of our way to ensure we don't piss off anyone by doing them.
- There's no uncertainty or debate about how they should be implemented.
- They are isolated, meaning they don't affect everything else in the game like balancing changes do.
- They require very little testing so they can easily be added last-minute.

On the other hand, the "small PK'ing QoL's" you refer to take days or weeks of our undivided attention just to make sure we don't fuck up on the specifics. The number of people who have clearly voiced their support for them can still be counted on one hand. There's opposition and disagreement, it's often very unclear what specifically needs to happen and they take a long time to test because they do impact everything else.


The way I see it there's two possible ways these changes will happen:

- Someone from the community goes through the effort of gathering and summarizing all the unstructured opinions. That way we don't have to do all the "market research", which is by far what takes the most time about PK'ing changes, and can just get on with implementing and testing.

or

- We do it all ourselves: read all the back-and-forth discussions, talk to people, try to come up with agreeable solutions, gather feedback, amend our proposals, gather more feedback etc until finally we reach an acceptable version we can implement. This is a very involved process for us, it's a big project by itself and there is no way we can do it while we're in the middle of another big project. There's only so much we can fit in our heads at any given time.

I understand that as a PK'er to you it probably seems obvious what needs to happen, but to us this is less than clear. Even with the various opinions and discussions posted in several threads it still takes us a long time to distill those into a number of specific changes that we know will be well-received. I'm not saying the community should do all this work for us, but please, at least don't go acting like this should all be super simple for us. It's not quite as easy as implementing one action on a ladder or KBD head.