Announcements

Join the ongoing conversation on Discord: https://discord.gg/w6Tpkp2

Please read the current update for instructions on downloading the latest update. Players with Mac versions of the game will not be affected, but you will have a slightly longer wait for your version of the new maps. Please make a copy of your character folder before running the new update, just to make sure you don't lose any of your custom work.

It looks like we can give everyone a list of minimum specs for running City of Titans. Please keep in mind that this is 'for now' until we are able to add more graphics and other system refinements. Currently you will need :
Windows 10 or later required; no Intel integrated graphics like UHD, must have AMD or NVIDIA card or discrete chipset with 4Gb or more of VRAM
At least 16GB of main DRAM.
These stats may change as we continue to test.

To purchase your copy of the City of Titans Launcher, visit our store at https://store.missingworldsmedia.com/ A purchase of $50 or more will give you a link to download the Launcher for Windows or Mac based machines.

Bug Tracking with Alpha/Beta Testing

3 posts / 0 new
Log in or register to post comments
Last post
Wed, 12/12/2018 - 11:56
#1
Mike Skoog
Offline
Last seen: 5 years 4 months ago
kickstarter
Joined: 10/09/2013 - 16:52
Bug Tracking with Alpha/Beta Testing

Do you a method for bug tracking during the Costume Creator/Alpha/Beta tests?

Since people will be reporting bugs, having a method to sort thru these could reduce the human time to sort the reports for duplicate errors.

If you don't have a method already in place, I suggest you give the public two methods to report any problems:
1) A free bug tracking software like Bugzilla.
2) For those who can't figure out the above software, a text based input form.

OR

When the user click a Bug Report menu entry, sub divide it into bug category sub-menus dealing with Costumes, Graphics, Mission Bugs, NPC errors, Annoying things, etc.

Then the Bug reports can have a bug category ID attached to make it easier to sort the bugs for the developers.

Mike

Top
Wed, 12/12/2018 - 17:08
Planet10
Planet10's picture
Offline
Last seen: 3 years 6 months ago
Joined: 03/23/2016 - 17:21
I would seriously hope that

I would seriously hope that they (MWM) have a system in place long long Loooooooonnnggg before now to address this issue.
The most effective way to temper the user base (who do not have a sight line into the process or bug data base) is to promptly and regularly communicate expectations for the build. This informs people as to what is known ([I]to cut down on the noise >> eleventy bajilion duplicate bugs[/I]) and where to focus testing ([I]to steer people away from known deficiencies / missing code[/I]). I would seriously hope that they have a robust reporting mechanism (that could transition into the full Issue #1 release), as having to coordinate two or more reporting mechanisms (forums, external bug tracking, etc) can quickly get out of hand.

Since only KS Backers will initially have access, I can only assume that some of that information is being released, but I suggest that it be widely distributed so the entire user base can keep up to speed on what is going on. That way when/if they participate they can be productive.

—

"Just, well, update your kickstarter email addresses, okay? Make sure they're current?" - warcabbit

Top
Wed, 12/12/2018 - 22:17
Mike Skoog
Offline
Last seen: 5 years 4 months ago
kickstarter
Joined: 10/09/2013 - 16:52
Thanks for the reply. It

Thanks for the reply. It looks like you have previous experience with bug reporting.

As you said, there needs to be a way to cut down on the noise.

Top