[1.2.1 & 1.2.2_beta] gene modded species keep the original name

[Kliwarrior]

First gene modded human become "human illustratum" (sic!)
Second and third ones become just "human" (so I've multiple but different "human" in my empire).

I've see something similar for alien species, where I discovered a couple of [add weird name here] in the same empire, the second one modded to another planetary preferences.

Note that I cannot rename the new species in the modding process (don't know if is a bug or a feature)

(BTW what is "illustratum" ?? It is not "Made illustrious" , is should be "illustris" .. )

 

[emperor_kk]

First gene modded human become "human illustratum" (sic!)
(BTW what is "illustratum" ?? It is not "Made illustrious" , is should be "illustris" .. )

At first I thought, it was a 40k reference but later when I saw other different additions, I realised it's just english turned pig-latin (which i dont really care it's kind of funny for those that can read them).

The "Illustratum" addition comes from the event of collonising a different planet type.

The same names are from modifying your own populace (or other populace in your empire)
I have the same issue, I modify my own populace and there is nothing differentiating one from the other, just the same name being endlessly repeated.

I'm not sure if it is a bug though or just a design ommision, I would bet on the later. I'll do a post on suggestions.

 

[ForzaA]

We're aware of the issue. Thank you for your report.

 

[Kliwarrior]

We're aware of the issue. Thank you for your report.

Thanks ForzaA , I wish you all the best in fixing all the stuff here..

 

[Kliwarrior]

@ForzaA , given that is not always easy to find out if an issue was already reported, and even for those "well known", there are multiple (daily) reports of the same problems (for example "empire X asks me to declare war on myself.." ) , might you consider to add a sticky & un-editable post of "Issues, which Devs are aware of" ?

In such a ways, users could take a look and (hopefully) not post same issues again and again.

 

[ForzaA]

It's been discussed several times internally, but for the moment we don't see a way to ensure such a list would remain up to date at a reasonable expense in manpower/time.

 

[emperor_kk]

It's been discussed several times internally, but for the moment we don't see a way to ensure such a list would remain up to date at a reasonable expense in manpower/time.

A flag on posts (reported as bug**=not relevant/ yes),
an instruction that if you have the same problem it is better to go and agree on post with same issue than open a new one
and a more interactive search feature*, would help though.

Right now there is a feeling that the more the merrier in bug posts. Personally I have a dislike in using forums for bug user-submissions due to the inability of consolidating user-submissions, not having a centralized location for end-user bug report and having to either build automations to transfer bug-data or do a lot of manual re-entry, but that's me and a entirely different discussion.

*ie. for empire x war declarations on myself, i easily found a lot of posts and i refrained for making a new one, for password in cleartext i didn't but you said it had already been reported which I believe it, but couldn't find it.
** reported as bug - means nothing other than "we know about it"

@Kliwarrior There is no easy way of conveying this type of information back from whatever bug-tracking service/ database/ ... , to a forum unless you invest in building an intermediate API or static interface between the two and/ or allocate someone to handle this manually and here comes the difficult part. The person that identifies, researches and/or accepts bugs is usually someone that has a more advanced skillset than your average forum mod (no pun intended), so having a skilled tester, spend much of his time on a tool that is not really applicable for this type of information (and VERY inefficient in tracking or consolidating this type of information) would result in a list that may be : A) incomplete, B) untimely updated, C) not easy to read .

I would love to be able to see a comprehensive list but I would be happy just being able to find if something is a bug or not, so as to keep the flow controllable and the whole task cost effective, enough to be able to nag about my X/Y weird bug not getting fixed and not feel bad about it.