Author Topic: Instructions for Beta Testers (PLEASE ACTUALLY READ IF A TESTER)!  (Read 49767 times)

Offline x4000

  • Chris McElligott Park, Arcen Founder and Lead Dev
  • Arcen Staff
  • Zenith Council Member Mark III
  • *****
  • Posts: 31,651
Re: Instructions for Beta Testers (PLEASE ACTUALLY READ IF A TESTER)!
« Reply #60 on: June 01, 2015, 10:43:42 pm »
I am about to start sending out the PMs.  If your name is on here and you don't get a PM from me within the next few minutes, then let me know!

Testers added on June 1st (Yellowshirts):
mooncows
Billick
P3X-639
TheokGrundor
Animorganimate
kasnavada
EzekielMoerdyk
skanx
stblr
MayhemMike
MooN
satoru
Elijah
DreadnoughtShanor
Azurian
Lysenko
eOSO
tim1983
Magus-k
Vordrak
Hampsmaine
Huw
FroBodine
Have ideas or bug reports for one of our games?  Mantis for Suggestions and Bug Reports. Thanks for helping to make our games better!

Offline x4000

  • Chris McElligott Park, Arcen Founder and Lead Dev
  • Arcen Staff
  • Zenith Council Member Mark III
  • *****
  • Posts: 31,651
Re: Instructions for Beta Testers (PLEASE ACTUALLY READ IF A TESTER)!
« Reply #61 on: June 02, 2015, 08:50:02 am »
Also now added to the yellowshirts: Razer98K

I had added him in another thread, but somehow mis-marked him on the spreadsheet, and so missed actually adding him to the game.  I'm really glad that he spoke up and let me know, and it's not a bother to me for anyone who does that.  Please do so!  If I miss anybody, it's always an oversight and not something intentional -- there's just a lot of people and a lot of data! :)
Have ideas or bug reports for one of our games?  Mantis for Suggestions and Bug Reports. Thanks for helping to make our games better!

Offline x4000

  • Chris McElligott Park, Arcen Founder and Lead Dev
  • Arcen Staff
  • Zenith Council Member Mark III
  • *****
  • Posts: 31,651
Re: Instructions for Beta Testers (PLEASE ACTUALLY READ IF A TESTER)!
« Reply #62 on: June 02, 2015, 09:40:00 am »
Ack!  Two other people I had said would be in late May builds a long while back, and I missed adding them to the yellowshirts wave:
wwwhhattt
iozay

But now they are.
Have ideas or bug reports for one of our games?  Mantis for Suggestions and Bug Reports. Thanks for helping to make our games better!

Offline x4000

  • Chris McElligott Park, Arcen Founder and Lead Dev
  • Arcen Staff
  • Zenith Council Member Mark III
  • *****
  • Posts: 31,651
Re: Instructions for Beta Testers (PLEASE ACTUALLY READ IF A TESTER)!
« Reply #63 on: June 15, 2015, 11:17:16 pm »
Testers added on June 15th (Blackshirts)
Rekka
Taravassal
doctorfrog
Chthon
LordStryker
MishTheFish
ghgl090
kokonut
qrter
dersquatch
DrGonzo
Valectar
Parmenides
Tormodino
greywolf1991
EvilMonk3y
Chriamon
AlgaeNymph
Vinco
Orelius
Jerebaldo1
rallythelegions
Teal_Blue
Tolc
Gwmngilfen
Have ideas or bug reports for one of our games?  Mantis for Suggestions and Bug Reports. Thanks for helping to make our games better!

Offline x4000

  • Chris McElligott Park, Arcen Founder and Lead Dev
  • Arcen Staff
  • Zenith Council Member Mark III
  • *****
  • Posts: 31,651
Re: Instructions for Beta Testers (PLEASE ACTUALLY READ IF A TESTER)!
« Reply #64 on: September 24, 2015, 08:54:08 am »
These are the old notes from the original post, haha.  I'll just save these here for posterity. ;)



There are no spoilers in here, and I'll be brief (well, brief for me ;)).

Current Status:
This is the very first batch, the valiant "redshirts," who will go forth and impale themselves on the worst of the bugs and confusion for the benefit of all those who follow.  I should have keys PMed to all of you within a few hours (waiting on a batch of keys from Steam, which I completely spaced out on and forgot to request until an hour or two ago).

Beyond that, specific things:
1. The new HUD is not in place yet.  The existing one will probably only be something you have for a day or two max.

2. I have a number of other things I'm working on, as does Keith.  A lot of your stuff regarding usability and the early game we'll get to as soon as possible, but I'm
also going to be extra slow in the next few days as I get some of the documentation done and things like that.  Please see the "Chris: For Soon" and "Chris: For A Bit Later" sections here.  I'll be doing most of the "for soon" stuff before I get to much of your feedback, and then the "for a bit later" stuff while getting to some of your feedback, and then beyond that your feedback is the primary thing.
2.a. Note that my options were basically to wait and finish those things and keep you out of the beta until then, or be a bit distracted from you at the start of the beta.  I figured the latter was preferable, all told.  I will still be reading all the mantis tickets, though!

3. The early game balance is something I've tested quite a lot, and I'm reasonably happy with it.  The midgame balance I've tested some, and there are some spotty bits I'm already aware of.  The endgame balance I have not tested yet at all in a "real" playthrough scenario, and there are various clarity issues with the various endgames.  All the pieces are there, but they are incredibly disorderly and not documented, just FYI.

4. I haven't yet run this on OSX or Linux, so it's possible this first build might not even launch on them.  If you can confirm whether or not those do work, then I'll fix it tonight if there is a problem.

Where To Give Feedback
On mantis, which is here: http://www.arcengames.com/mantisbt/

Key notes:
1. Please only report one issue per mantis ticket.  That way we can close the tickets when they are done, versus having half-done tickets all over the place.
1.a. That said, if it's something like "here are 30 typos," obviously that is one mantis ticket.  It's a judgement call on your part, but if you think that we're extremely likely to address the entire set of issues at once, then it's one ticket.

2. It is possible to upload files on mantis, though some folks miss that.  It's there in the middle of the page after you make your initial submission.  You can continue to submit more files as much as you need as discussion continues.

3. Please please please include a savegame and steps to replicate where relevant. :)  It's almost always relevant.  We don't need screenshots or video unless it's something really strange that you think we won't be able to easily observe another way.  But a savegame and instructions lets us just pop into your game, see the problem, fix it, test it, and then mark it resolved.  The observation and testing steps take 90% or more of the time for us if you don't include savegames.

Anyway, thanks. :)

What Sort Of Feedback?
Honestly, whatever you want to tell us.  If it's feature suggestions, then sure.  We might not do them or might not do them until far into the future, but it never hurts to submit if you've got an idea and you think it's cool.  If I do wind up closing a lot of your tickets as "won't fix" or "working as intended," please don't be disheartened.  I'll leave a brief comment to explain why, and the fact that you have a lot of closed tickets does not reflect in any way badly on you.  It's all good!  No pressure, really.

Now, the one exception: really long stream of consciousness narratives.  Those tend to be very hard for me to read quickly, and me being able to parse information quickly is a pretty important thing when it comes to moving through the beta.  You guys will outnumber me hundreds to one, literally, by the time this is over.  If you want to share longer narratives with other players in the forums and have a long discussion with them, absolutely!  No problems. 

If you come to some sort of consensus, or if you want to float specific ideas past me either way, then please just make mantis tickets that are specific potential action items.  Or that are specific problems that you had (confusion here, bug there, balance there, etc).  I'll take part in some longer discussions, but I won't have time to read most of them just because I'll actually be working on the game, but I will read every last mantis ticket that's in the style requested above.

These are just some guidelines on what to expect based on what has worked in the past.

Oh, Please Do Remember I'm A Human
If something sucks, I want to know about it.  But!  I'm not a robot.  So if you can tell me it sucks -- clearly, so that I know you mean it sucks -- without bludgeoning me emotionally, that would be best for all of us.  When I get worn down emotionally by overly-negative stuff, I get slower.

Basically think of it like this:

Healthy feedback: "Thing A is no fun at all, or is broken or whatever, and probably needs attention.  Possible resolutions might be XYZ, or I don't have ideas but what specifically is bugging me is 123, and addressing that would probably make this fun/functional/whatever."

Toxic feedback: "Thing A sucks, I don't know what you were thinking.  I'm not having any fun at all."  (NB: Even if you're not having any fun at all because of some issue, a better way to say it is "I can't get past this issue to really evaluate the rest of the game, because this one thing is bothering me so very much.")

TLDR: I can take the heat, I'm open to all feedback, but only when I feel like you're on my side.  If I feel like you're going "this Chris guy is actually an idiot, why was I ever excited about this," then I start going into a death spiral if that happens enough.  Past a certain point in the beta I get a lot more confidence and that becomes less of an issue, but whenever I'm first unveiling a new game it's a really emotionally tense thing for me.  Don't hide the truth from me or say things you don't mean, but if there's something you hate then please give me the benefit of the doubt that we can work through it together, and approach it from that angle.  It will be a lot happier for both of us that way!

What Are We Doing Right Now?
Mantis is where you make your submissions of ideas to us, and I categorized them and so forth there.  However, I then pull those into a "list backlog" that is a more short-term todo list in an order that shifts around from day to day based on what new information comes in.  That list backlog has always been private in the past, but this time we've decided to share it with you so that you can get a better idea of what is coming: https://docs.google.com/document/d/14XQ61PpOfTHiusfdy0D6Vjq2OjNN04GkKddpYV7ZrJE/edit?usp=sharing

So, whenever "now" is, that page lists what we're doing. :)

What's Changed Lately?
Whatever it is, you can read about it here: http://arcengames.com/mediawiki/index.php?title=Stars_Beyond_Reach_Beta_Release_Notes

Tips
You don't owe us anything for being a part of the beta, in fact my view is that we owe you.  The free copy of the game that you get is a small token that we're able to give back to you.  Your feedback really is what takes the game from being pretty rough at first beta, and then getting to fully polished at 1.0.  That said, if you want to leave a tip, we do have a way for you to do that: http://arcengames.com/tips/

Giving us a tip is not required to get into the beta, nor will it get you into the beta -- though getting into the beta honestly shouldn't be a problem for you anyway, at this point, if you have the interest.  We're only taking a certain number of people per batch, but you should have no problem getting into one of the batches.  My honest preference is that if you do feel inclined to give a tip, you actually wait until you're in the beta and make sure you still feel that way. ;)
Have ideas or bug reports for one of our games?  Mantis for Suggestions and Bug Reports. Thanks for helping to make our games better!

Offline x4000

  • Chris McElligott Park, Arcen Founder and Lead Dev
  • Arcen Staff
  • Zenith Council Member Mark III
  • *****
  • Posts: 31,651
Re: Instructions for Beta Testers (PLEASE ACTUALLY READ IF A TESTER)!
« Reply #65 on: September 24, 2015, 03:55:38 pm »
Testers added on September 24th (Redshirts V2, previously going to be known as Greenshirts)
Traveller
Tomasdk
ElektroSMF
Nubbify
Tridus
donlol
darkarchon
hadberz
Genomic
gnosis
Firemad
hapexindustries
Torchwood202
Peons
Rendon
Diji
Paracosma
Despayre
bobsky
mrvole
Ingros
Greywolf22
KaidenOZ
Genosse
dfinlay
SashaNein
d10sfan
Ravachol
Entvex
rjblackwolf
Have ideas or bug reports for one of our games?  Mantis for Suggestions and Bug Reports. Thanks for helping to make our games better!

Offline x4000

  • Chris McElligott Park, Arcen Founder and Lead Dev
  • Arcen Staff
  • Zenith Council Member Mark III
  • *****
  • Posts: 31,651
Re: Instructions for Beta Testers (PLEASE ACTUALLY READ IF A TESTER)!
« Reply #66 on: October 01, 2015, 03:05:39 pm »
Testers added on October 1st (Blueshirts V2)
Smithgift
tassadarpaladin
YukaTakeuchiFan
NullDragon
Panzeh
Groomy
Cyprene
Pluto011
Rythe
Julius
Morslok
Turbokretzsche
jaxxa
anastase
ElOhTeeBee
Mal
ajhager
Vesson
mightymike2035
Grey-fox-13
gia
jabbawocky
Chazn2
DFox83
Matt Damon
Have ideas or bug reports for one of our games?  Mantis for Suggestions and Bug Reports. Thanks for helping to make our games better!

Offline michaelweber

  • Newbie
  • *
  • Posts: 1
Re: Instructions for Beta Testers (PLEASE ACTUALLY READ IF A TESTER)!
« Reply #67 on: October 24, 2016, 09:19:16 am »
This is really nice. Thanks for the information.

 

SMF spam blocked by CleanTalk