Pyro Emitter - missing statistical information/not listed

Bug Report Section Texts
#1

Bug report:

 

Issue 2:

Pyro Emitter:

Screenshot: 5400 meter firing range should also be listed under statistical information above, not just in the description.

Statistical information missing/not listed: Firing range (max.) 5400 m

n6f6b.png

#2

so you are just asking for…

urMNQcF.png

?

#3

50 minutes ago, QACinnamonTroll said:

so you are just asking for…

urMNQcF.png

?

Correct!

This module is not the only one, but one of many. I would be pleased, if all Super-Testers would actually go through all of them.

There are not so many. It’s a minor issue and easily corrected.

 

For example, there is a vital information missing, could be because of lack of space and clumsy and limited interface.

It’s never stated, if you replenish a repair/combat drone on Engineer, what range it needs to be, that it will apply to allied target, restoring their shield.

So, the information missing in this case is “effective range (max.)” A lot of people have asked me that.

To this day, I still do not have 100% correct answer!  ![:017:](<fileStore.core_Emoticons>/emoticons/017.gif “:017:”)

#4

6 minutes ago, Koromac said:

Correct!

This module is not the only one, but one of many. I would be pleased, if all Super-Testers would actually go through all of them.

There are not so many. It’s a minor issue and easily corrected.

 

For example, there is a vital information missing, could be because of lack of space and clumsy and limited interface.

It’s never stated, if you replenish a repair/combat drone on Engineer, what range it needs to be, that it will apply to allied target, restoring their shield.

So, the information missing in this case is “effective range (max.)” A lot of people have asked me that.

To this day, I still do not have 100% correct answer!  ![:017:](<fileStore.core_Emoticons>/emoticons/017.gif “:017:”)

You are becoming THE proffesional bug reporter  ![:015j:](<fileStore.core_Emoticons>/emoticons/015j.png “:015j:”)

well, if you start now, you might actually make it before 2017 with all those bug reports ![:D](<fileStore.core_Emoticons>/emoticons/006j.png “:D”)

 

btw, there are no “Super Testers” anymore cuz its not obt anymore, but feel free to call them like that ![:D](<fileStore.core_Emoticons>/emoticons/006j.png “:D”)

#5

5 minutes ago, QACinnamonTroll said:

You are becoming THE proffesional bug reporter  ![:015j:](<fileStore.core_Emoticons>/emoticons/015j.png “:015j:”)

well, if you start now, you might actually make it before 2017 with all those bug reports ![:D](<fileStore.core_Emoticons>/emoticons/006j.png “:D”)

 

btw, there are no “Super Testers” anymore cuz its not obt anymore, but feel free to call them like that ![:D](<fileStore.core_Emoticons>/emoticons/006j.png “:D”)

Well, I am not done with bug reports. More are waiting. I reported some of them in [1.4.0 update discussion](< base_url >/index.php?/topic/32197-star-conflict-140-evolution-discussion/&do=findComment&comment=386210).

Let me show you about the issue I talked about. Missing information about repair/combat drones on Engineer.

359y3bd.png

There is no info about max effective range for repair/combat drone, when replenished next to an ally or more allied targets.

#6

Should I make another bug report, or is the issue understood?

I am asking for this statistic or description to be added:

Range: 5400 m, may vary depending on the module.

#7

may be that way, may be other way… don’t important, I think