Quest 3 Stage 14 Typo?

Flashman014 · Post by **Flashman014** » Sun Mar 20, 2016 5:05 am

Transporter ALC Stage 14

The quest message says to build the power supply exactly 350 meters below the object, yet the objective marker is at 3500 below. Plus, 350 is practically still in the object. Typo?

Also, is there a designated bug reporting area? If not, why not?

captainedwin · Post by **captainedwin** » Sun Mar 20, 2016 6:13 am

Hiyah neighbour!

http://www.starwraith.com/forum/viewtopic.php?t=12248

found it!

Post by **Marvin** » Sun Mar 20, 2016 4:08 pm

The confusion is in how the waypoint indicator measures distance versus how the Build constructor measures distance. The easiest way to build or deploy an object specified in a quest is to set your heading and pitch to zero then jump to the location. You can then use the numbers in the Build menu (green, upper-right corner) to adjust your position.

Check here for further information: http://www.starwraith.com/forum/viewtop ... #pid182724

Flashman014 · Post by **Flashman014** » Mon Mar 21, 2016 12:11 am

From post: 186841, Topic: tid=12548, author=Marvin wrote:The confusion is in how the waypoint indicator measures distance versus how the Build constructor measures distance. The easiest way to build or deploy an object specified in a quest is to set your heading and pitch to zero then jump to the location. You can then use the numbers in the Build menu (green, upper-right corner) to adjust your position.

Check here for further information: http://www.starwraith.com/forum/viewtop ... #pid182724

No, I think the confusion is that the quest text says 350 and the quest target indicator sits squarely at 3500. I think there's a missing 0 in the text. I'm not talking about the Build Constructor at all, just the little purple indicator that the quest pops up in space. You sit inside the hyper gate thing and look at the quest target and it says 3500 meters. I'm not having a problem completing the mission, I'm just pointing out what looks like a glaring typo to me.

How does the Build Constructor measure distance differently? I look at my position on the Navigator screen and again on the Build screen and it says the same thing. Isn't a meter a meter, no matter what you're doing with it?

Flashman014 · Post by **Flashman014** » Mon Mar 21, 2016 12:25 am

From post: 186821, Topic: tid=12548, author=captainedwin wrote:Hiyah neighbour!

http://www.starwraith.com/forum/viewtopic.php?t=12248

found it!

Yeah, I'm aware of this thread that's been buried in the forum. I've even posted in it a few times. But don't you think there should be a spot that's a little easier to find and even browse through? It wouldn't even be hard to make. There's already a Technical Support section, so the hierarchy could go something like this: Tech Support -> Bug Reporting -> Evochron -> Legacy. Or something to that effect. That way people wouldn't have to search through a long, convoluted thread with 1000 different bugs in it, with each one having 100 responses to it. It could be so nice and neat and easy to use, therefore easy for Vice to address each issue.

Post by **Vice** » Mon Mar 21, 2016 2:43 am

The best way to report bugs is to me directly via e-mail (starwraith.com > contact) with a profile attached and steps to duplicate the issue. It's the primary mechanism I use for tech support and bug report management (I have a local sorting and listing procedure to handle them).

If you're not sure an issue is a bug and would prefer peer review of it for analysis as part of the reporting process, then posting a thread on the forum is a good way to do that (tech support when using the posting guidelines for that forum or just in the game's specific forum). A long thread is indeed not my preferred way to try and sort through such issues

So either a new thread if you want others to review it and comment or a direct report to me are generally the preferred ways.

No, I think the confusion is that the quest text says 350 and the quest target indicator sits squarely at 3500. I think there's a missing 0 in the text. I'm not talking about the Build Constructor at all, just the little purple indicator that the quest pops up in space. You sit inside the hyper gate thing and look at the quest target and it says 3500 meters. I'm not having a problem completing the mission, I'm just pointing out what looks like a glaring typo to me.

How does the Build Constructor measure distance differently? I look at my position on the Navigator screen and again on the Build screen and it says the same thing. Isn't a meter a meter, no matter what you're doing with it?

The quest text is correct. It is calibrated with the build system, which is calibrated to the in-sector coordinate system (what you see on the nav console). Since you use the build system to place the build point at a location in space using the coordinate system, you need to apply 350 to both (green readouts in the build console, coordinate readouts in the nav console, both using the same scale). These are synchronized in decameters (greater distance, smaller/easier to manage values). The target range system uses meters, so it displays a 10X higher precision level in its value (3500 meters = 350 decameters). You don't need to contend with the target ranging system when building, unless you want to compare for some reason. Just line things up with the build/coordinate system and 350 is the correct coordinate distance you need to apply.

Flashman014 · Post by **Flashman014** » Mon Mar 21, 2016 3:14 am

The quest text is correct. It is calibrated with the build system, which is calibrated to the in-sector coordinate system (what you see on the nav console). Since you use the build system to place the build point at a location in space using the coordinate system, you need to apply 350 to both (green readouts in the build console, coordinate readouts in the nav console, both using the same scale). These are synchronized in decameters (greater distance, smaller/easier to manage values). The target range system uses meters, so it displays a 10X higher precision level in its value (3500 meters = 350 decameters). You don't need to contend with the target ranging system when building, unless you want to compare for some reason. Just line things up with the build/coordinate system and 350 is the correct coordinate distance you need to apply.

Well, then maybe my issue is that the quest text isn't specific. It simply says "build the power supply 350 meters below the object." It doesn't say decameters, and it doesn't specify coordinates. It reads to me like "count 350 meters from the object and build there." If it's meant to say coordinates within a sector, it should specify that. If it's supposed to mean decameters, it should say decameters. To my recollection, I've never even seen the word "decameters" inside the game, only on the forum in reference to the game. Perhaps I misread, or am mis-remembering the actual verbiage, but I don't think so.

As far as the bug reporting goes, I only mentioned a dedicated place for bug reporting so people aren't reporting the same bug multiple times directly to you. Players could look at the bug report forum, scan through the bugs for the current version and see if they're being redundant or not. If so, they can simply comment something like "me too, here's the conditions for my case, etc." on the corresponding bug report. I personally would like to be able to look through other people's bug reports to see if I'm the only one with the problem, or if it's already been addressed, so I can at least troubleshoot my end of things before I take the time to try and articulate the problem in detail to send you an email. You see what I'm saying? But, at the end of the day, it's your game and your forum. Whatever works for you, I suppose the rest of us will deal with.

[Edited on 3-21-2016 by Flashman014]

Post by **Vice** » Mon Mar 21, 2016 3:37 am

It would help to clarify things if it did say 350 decameters or something like 'build at a point 350 below'. I'll check with the script author of that quest and see what they'd like to do.

Most bug reports/correspondence come in via e-mail, whether or not I've provided a dedicated place for them on a forum in the past (as has been done years ago). Many aren't actually bugs (user error/misunderstanding or system problem), some are duplicates, and others are solo reports. But my local organizing system helps me sort through such things. Bug reports are generally few enough and enough get posted on the forum that things generally already work out like you describe. And once a bug is fixed, it's gone (generally indicated in a changelog when fixed). If it was a much more frequent occurrence and/or duplication much more of a problem, some kind of online checklist would likely be helpful. The current volume is pretty manageable for me though.

Most of my attention and time is spent handling e-mail and coding, so that's where my attention is focused already... I generally get to this forum during compile waits or other times of the day. The technical support forum definitely helps for that side of the equation since system problems (drivers, hardware, security software, Windows problems, etc) can often be resolved by peer help/my help and remain visible for others to see. Those can remain perpetual issues and are good to have solutions available for.

Post by **Marvin** » Mon Mar 21, 2016 4:21 am

I had Vice roll back a test profile and checked the distance at stage 14: the Build menu does, indeed, display -350 for the Y offset. If that's in decameters, then both the quest text and quest tutorial need to be changed. Probably in more than one place ....

Post by **Marvin** » Mon Mar 21, 2016 7:18 am

The number -350 is what you see in both the Build menu and, if you're at the exact build location, what you see as your current Y position on the Nav map. But, if you set a waypoint at the portal before moving to the build location, the waypoint will display a distance of 3500. Units. Meters. Whatever. I knew this ... it just got by me. But the correction to the quest script shouldn't be to add a zero the the 350 meters ... that would confuse anyone using the Build constructor ... which is the most accurate way to build. So the change will most likely be made to the label, changing it from meters to something else ... something which reflects the actual distance relative to sector increments.

Flashman014 · Post by **Flashman014** » Wed Mar 23, 2016 7:26 am

Thank you for looking into this. I didn't really mean to make such a big deal about it, but I'm glad it's being addressed, if for no other reason than clarity's sake. Thanks again, Vice, for making and maintaining this great game. And thanks to you, Marvin, for always being so quick to respond and such a good forum mod/veteran player/advice guy. This really is a very complex game in some aspects, and it stands to reason that a player might need a little clarification now and then. Cheers to a good, active forum!

[Edited on 3-23-2016 by Flashman014]

Post by **Marvin** » Wed Mar 23, 2016 4:58 pm

Thanks. The changes should be in the next release of the game.