Dark star bonus lost

[slender beacon]

Found a new bug. Hurray... if 4 players try to join a drr one is kicked out. However he also lost this bonus when he got rejected from that drr. (get the message that this drr is full).

How to reproduce it: Try to join with 2 players via channel message the same drr that is already 2/3 full and one will get rejected and this bonus 100% artefact bonus is lost. Lucky this bug doesnt affect the croit as well.

[gritty creek]

Makes sense, it eats the bonus the moment a queue is attempted
Would follow the logic of losing the bonus when starting and not completing a scan

(Not saying it’s not a bug, but logical behavior)

[sour aurora]

lost dark star bonus w\o being able to join drs9. star id BTK 2977
3 of us corpmates queued up on discord. when we scanned and joined, a random player also joined. so 4 tried to join. it disallowed me and stole my dark art bonus 😐 (android, not steam)

[fair flint]

What is logical about canceling the scan in progress and losing the bonus? Please tell me.

[gritty creek]

What they experienced is a logical extension of the current behavior where the bonus is used the moment the button is clicked

Not that clicking the button being the action that eats the bonus is a logical way to do it

[fair flint]

@gritty creek But if you cancel the scan, then the bonus should return, same as hydrogen. I guess two different logics are presented here. Hydrogen is returned, so why not the bonus.

[gritty creek]

I’m not saying that’s the way it should be
Just that what they experienced is not unexpected with the way it is currently

[pulsar axle]

💩

[zenith spruce]

@dev fix this please it is easy.

[final coral]

@players understand and deal with it, it's easy.

[zenith spruce]

well, that's an easier fix, yet putting the burden on customers when dealing with a shitty design is a solution that frustrates the user 🙂 A dysfunctional website can be used, a dysfunctional dev car can be driven, doesn't mean that they should stay as such 😉

[final coral]

It frustrates you and what 3 others in this thread. Hardly a big enough sample size to call it dysfunctional. If you think that's what it is and you're still using it it then you're proving the benefit of using the app outweighs the "frustration"

[zenith spruce]

You don't need a statistical study to call a feature dysfunctional. Of course it is a minor deficiency which does not have a major impact on the satisfaction, yet it is perceived as an irritant (yeah for me and 3 others which btw makes a fair percentage of the people active in the thread lol) and could be easily fixed (2h to 4h work with a messy code).

everything in product maturity is a matter of priority vs resource availability, of course there might be things which are judged more prioritary, but since we do not have visibility on the sw updates planning or version management, all that can be done is asking and contributing to consolidating a backlog

this is retex on user experience, and it is useful to improve any product

your comment, conversely, adds no value to the discussion by just arbitrarily declassifying an irritant for somebody to an issue which should not be relevant to the devs

[gritty creek]

IMO it could easily be more then "2h to 4h work" even without messy code. We have no idea what else it could impact, what it would take to make that issue not happen, what exploits various "fixes" could open up, what new bugs could be introduced

[gleaming kite]

https://discord.com/channels/255083954036670464/1200318244406444114 there is another thread w/ lost bonus complaints

[rustic pine]

Is this a bug? Yes
And that's all there is it. IT doesn't require discussion on ways to mitigate it, past the first person to do it anyways.

It's a bug. It should be fixed. We've done what we can.

[zenith spruce]

true, i have been oversimplicistic, yet I believe it is an easy fix vs many majors which might be more needed

[final coral]

Is it a bug? Maybe:

[zenith spruce]

Idk, I have been speaking of irritant feature more than bug but depends on your definition of those 😁

[final coral]

The developers intention matters more than how you feel.

Funny how the definition of the word you're using changes suddenly to support your position...

[zenith spruce]

when did I speak of "bug"?

(i wanted to reply to the 2nd part of the comment, sry)

that said I am not going to war, I report a feature as dysfunctional and the devs are free to take my retex or not vs cost of eventual change and their liking

[final coral]

The thread you're in, the 4th word of the original poster. Are you lost? Do you need help finding the "dysfunctional irritations thread"?? 🙄

At least you admit it's up to the dev to decide instead of making demands.

[zenith spruce]

I thought the thread moved from assessing that the original post is not a bug to discussing how annoying is the loss on search cancel?

[final coral]

Uh no?

[zenith spruce]

not me?

at any rate I really don't see where is the point of your polemics - be it a bug or an irritant devs are under no obligation to do anything. I think it is useful to speak of things that one feels should work differently to improve the general user experience. This kind of irritants are not related to game balancing, they are not subjective, they can be solved and the result will be neutral for those who don't care and positive for those who see the feature as an irritant. There are only winners with an easy fix, so I really do not see why that should not be proposed ^^"

[final coral]

What irritates players of a game on the internet is inherently subjective. Describing an outcome for players who don't care and those who do is describing subjectivity.

[zenith spruce]

To be or not to be... But you are right, they are. Wrong choice of words on my side 😄