Just a little something that we put together to show a glimpse of what is happening behind the scenes.
Hope you enjoy
Just a little something that we put together to show a glimpse of what is happening behind the scenes.
Hope you enjoy
You guys shouldnāt have hired popolion devs in the first place. jk!
Buā¦but⦠Popolions!
Heās head of our QA team btw in case anyone wanted a little more background info.
Errmm⦠Everyday might be a bit of a tall orderā¦
How about āas fast as I can bribe one of our artists with donuts?ā
Iāll let you have your pick if you manage to drop by sometime.
do you have popodoges too?
Nope, none of those⦠Sorry
Maybe a Battlebird or twoā¦
@STAFF_Ethan @STAFF_Amy Hey guys, a little off-topic but I think will help you guys handle game suggestions and bug reports better moving forward.
In the website, maybe you can add and maintain a section that lists all collective player suggestions (only ones that makes sense or most hearted) as well as bug reports, preferably with a datestamp (date it was first reported/suggested) and a short description (if it requires a more detailed description you can simply link to the thread).
Also, include a column labeled āStatusā where you can put whether an item is āAcknowledged (or maybe Pending)ā, āIn the works (w/ date on when it started)ā, āCompleted (w/ date)ā, "Canāt be done (w/ date).
So itās something like this:
2 sections: āSuggestionsā and āBug Reportsā
Columns:
Suggestion/Bug || Description || Status
For example:
[2017-02-23] Rework transcendence || Maecenas augue tellus, laoreet at gravida at, facilisis in sem. || [2017-03-28] Completed
This list you guys can update weekly or monthly as long as inputs from players keeps pouring in.
I donāt know if this is too much additional work for you guys but this kind of transparency will really help the players understand the gameās current state and also avoid repeat reports/suggestions in the forums as well as through tickets.
Putting myself in your shoes, it maybe is a little intimidating in the beginning just thinking about starting it but in the long run this will greatly benefit you guys as well.
@ZeroFoxGiven Funny you mention that because, believe it or not, we are actually in the process making some plans to make the forum categories a bit less cluttered and suchā¦
As youāve mentioned though, thereās a lot on the forums so give us some timeā¦
even real lyf popos?
I did see a dog wearing something similar while going to lunch last week but nopeā¦
aww. Popokim is definitely there. Too bad my Popokimās always get deleted.
With 2 testing phases, 90% of the patches still brought bugs. Hmmā¦time to fire somebody?
Warning: Trying to balance coffee on your head as GM Papaya demonstrates can result in injury.
@mosesfetalvero Errmmm⦠No comment�
@silverx093 Well, an issue we have is that some bugs donāt appear in either testing sessions even when we specifically test for them.
We perform tests on Steam beta servers as well as in-house servers, but somehow pushing them to live servers is always a bit⦠shall we say messy? not to mention a lot of bugs donāt even get fixed in kTO
@MyriadColors It was stale coffee that I was about to exchange for some new brew, so no worries! Even so, donāt try it at home peeps.
Are you seeing noticeable success with the KTEST server?
Wellā¦if you are making the developer test the game himself, it is going to be hard finding the bugs. From your picture, I can imagine the tester team is either only one random person or just the developer. Why dont the GM join the test before release?
@Queue Iāve overheard that they are getting some good data(since Iām not on the team that monitors that), but that data is a bit more kTOS specific. You may have noticed from our post on the kTOS meetup that kTOS players have different views on quite some things.
@silverx093 I only included one person to represent the QA(tester) team since it would be impractical to draw everyone working in the office. It doesnāt mean that it is really just 1 popolion.
Also, something that I canāt really tell you in a short comic is that thereās a dev team, a programming team and a tester(QA) team which are all composed of different people. The GMs also join in on testing the broader aspects during the second phase of testing.