Dev Tracker

Hellooooo! It's time for another round of fixes. Far from all of them, of course, but here are the latest changes:


Fixed!

I took a look to be sure, and this has already been removed from the random name generator, so should no longer be an issue.

All relevant "Friend" attire descriptions have been fixed. Go forth and enjoy your friends!

Fixed, and also removed an unnecessary comma.

Fixed!

Oops, it's so tough to keep track of all these strains coming out of the Scarred Wasteland... This has been corrected!

These have both been fixed!

Fixed!


Then, to tackle the list from @Limanya -
Both instances fixed.

Fixed!

Updated!

Fixed!

Not nitpicky, I'm always happy to keep things consistent! I changed the hyphen out to the comma for simplicity's sake.

Fixed all instances (well, the ones reported here, I'm still chasing around various capitalization errors with a hammer).

Fixed!

Fixed, changed up the description here to be cleaner overall.

Fixed, also removed an unnecessary comma.

Changed to keep it consistent for the flow of the description.

Fixed!

Fixed!

Fixed!

Fixed, I shifted the sentence around to be clearer.

All of these questions have been updated for consistency and to remove the implication that Tomo has a weird grudge against merchants.

The hyphen's all right in this case, but the em dashes have been fixed!

Fixed!

Names capitalized.

Name capitalized and plural corrected.

Name capitalized.

Name capitalized.

Fixed the capitalization for "Waterway", but I've left "noggle" for now as it's a general species term.

Name capitalized.



That's all I've got for now! Many thanks to all who've called out errors here, we appreciate it. Keep those reports coming, I'll keep digging through as I am able!

The following corrections went in today:

• Primary: Chorus (Bogsneak F) - The pattern offset was corrected.
• Primary: Chorus (Mirror M) - The base color of the body was using standard basic base color rather than the unique base colors of this gene pair.
• Secondary: Choir (All Nocturne) - The neck frill shadow were restored.
• Secondary: Choir (Obelisk H) - A missing mane fade was added in to match the adults.
• Tertiary: Thorns (Dusthide) - The edge accent color of each spine was added in to be consistent with thorns on other breeds. The belly thorn placements were adjusted.
• Chorus | Choir Edges - When viewed against a dark background, some of the colors had a pixel halo. This halo has been removed.
• Chorus | Choir Colors - Generally speaking, the unique colors and dark accents of Chorus and Choir were cnsidered working as intended. However, we adjusted some of the exceptionally dark blacks to still be very dark, but backed off of that extreme by a small amount. This should result in keeping the high contrast. Here is a visual example of the changes that occured to the outline colors. The adjustment affected these colors only, only to the outline, and did not affect any of the gradients or accent colors.
  

Hello everyone! First, thank you to everyone who took the time to share your thoughts constructively about the topic of the thread.

Second, as this thread is technically about the gene fix process, and we've asked folks to please send us their feedback on that through Contact Us, we're going to go ahead and lock this thread now. Thanks again!

@TacoTequila, one was in the right place and the other was being a bit stubborn about moving over. Both are now where they should be now. Thank you for letting us know!

Thank you, @Hazekid, for the redirect to the Backlog - Modern Gene Errors thread! Locking the thread now as this is an error report. Thank you!

Hi @Yokudl, from what we've been able to verify, Zendesk does not and is not blocking users by region or country. They're a company that provides customer support related software and services for businesses. If your country is blocking its citizens from accessing Zendesk, that's outside of our control. Contact Us is and remains our official avenue for support and feedback.

Replies bringing up Fathom F Secondary have removed. Player feedback on the fixes is still under discussion and review. Thank you.

A new gene begins displaying on modern dragons. New achievements, den slots, and Ancient parallels appear!

---

Chorus & Choir
Chorus and Choir genes are now appearing on Modern breeds and Veilspun dragons! These primary and secondary genes can be purchased in the Treasure Marketplace, and apply a vibrant stripe and teardrop pattern across the body of your dragon

---

New Achievement
Today the Acclaimed Achievements Association has updated its records to include achievements for hatchling modern dragons with Chorus and Choir.

---

Mosaic & Breakup
The primary and secondary gene pair, Mosaic and Breakup, are now appearing on Aberration, Banescale, Dusthide, and Veilspun dragons! These primary and secondary genes can be purchased in the Treasure Marketplace

---

Cherub & Seraph
The primary and secondary gene pair, Cherub and Seraph, are now appearing on Dusthide and Veilspun dragons! These primary and secondary genes can be purchased in the Treasure Marketplace

---

Thorns
The Ancient-exclusive tertiary gene, Thorns, is now appearing on Banescale, Dusthide, Gaoler, and Sandsurge dragons! This tertiary gene can be purchased in the Treasure Marketplace

---

Hibernal Den Tasks
Dragons have found new ways to use new resources found in Boneyard to renovate and expand their dens. 5 new Den Tasks are now available.

• Boneyard Boons
• Boneyard Buffet
• Ossein Resources
• Anatomy Archive
• Warded Remains

---

Riot of Rot
The twelth annual Riot of Rot will begin on October 27, 2024, and we're running a skin and accent contest in celebration! Click here for more information!

---

Additional Updates
We are continuing to review feedback from the Fathom gene corrections and gene correction communication and threads overall. Feedback about the gene corrections process should be sent directly to us through Contact Us.

In the meantime, if you're interested in keeping up with gene fix updates, be sure to enable alerts for the tracking thread and/or bookmark the URL for the Undel-specific filter in the Dev Tracker, which will show you every update Undel posts and when.

• The icons for Primary Gaoler Gene: Mosaic and Secondary Gaoler Gene: Breakup were updated to match the modern and other ancient counterparts.
• The issue that caused yesterday's log-in modal (or pop-up) is resolved. Please see our post in the Bug Reports forum for more information.
• We had an update and additional information about the now-completed Fathom F Secondary technical fixes.
• The update to the Auraboa lore story, Ancient Arboriculture Observations, is live! You can read more about this update in the Flight Rising Discussion forum.

Hiveworks and Venatus were able to identify the source of the ad with the help of your direct reports and HAR files. They deactivated the source of the ad yesterday and let the advertiser know there are fixes that need to happen on their side with respect to their configuration.

Your browser cache should have cleared any cached versions of the ad by now. If it hasn't and you're served this ad with the pop-up again, please clear your browser's cache and cookies.

Generally speaking, you shouldn't enter information into a random log-in window or pop-up/modal. Close out the browser and report the incident to the site operator, which is what you've done. They will determine if it's a malicious issue or a configuration error that, let's say for example, presents the advertiser's own network log-in window to their advertising audience.

Thank you to everyone who brought this to our and to Hiveworks' attention!

The following fixes went in today

We're aiming for mid-week now, I'm sorry. Trust me, we're not thrilled with this delay either, but I promise you we're working on it and it's on the way!

Hi @hypnotheque and @EmberArcane! Mutton took a look at the reported issue and responded to Bug Reports forum thread:


Hiveworks has an instruction page here on how to capture HAR files and report rogue ads. Thank you for bringing this to our attention!

Hello all,

It appears that there is an advertiser that has misconfigured their servers, so when an ad tries to load a resource from their server (probably an image or a script) it returns an HTTP 401 and makes your browser ask for a username/password. You should be able to safely cancel out of the login popup. I am sorry for the annoyance and potentially alarming nature of this issue.

If you are able to reproduce the issue reliably, and are comfortable using the developer tools in your browser, there are instructions in the Advertising Report Thread on how to capture a HAR and send it to Hiveworks to help them track this one down.

Please check the known issues and working-as-intended sections before making a report!

This thread is to track any gene errors that occur with the new Chorus and Choir genes for modern and veilspun dragons.

In this thread, players may report any errors they encounter with the new genes. These can be technical errors, or consistency issues. This thread is intended to focus on these potential errors so that they can be addressed swiftly.





Please report any errors you encounter and we will do our best to correct them in a timely manner. This thread will close out 45 days after release, on November 29, 2024. After this time, players may report technical issues with these and other gene errors in the Modern Gene Error Backlog Thread, but further consistency issues will not be accepted for review and will be considered working as intended.

---

Note that it may take a short while for the site's internal image cache to reflect the corrected image assets.

Corrected Issues

Known Issues

Investigating (Not sure if issue or not)

Working as intended

---

I will be deleting reports that are not relevant to the genes released in the Chorus and Choir update, reports that have been corrected, reports are not considered an issue, duplicate reports, and discussion or chatter as I encounter/investigate them to keep the thread current with gene reports only.


This thread is accepting reports on the following genes only:

We are continuing to review feedback from the Fathom gene corrections and gene correction communication and threads overall. Feedback about the gene corrections process should be sent directly to us through Contact Us.

In the meantime, if you're interested in keeping up with gene fix updates, be sure to enable alerts for the tracking thread and/or bookmark the URL for the Undel-specific filter in the Dev Tracker, which will show you every update Undel posts and when.

Hiveworks is actively working on tracking down the bad ad source. They've received multiple reports with the HAR files as requested which have been very helpful. As of right now, they've had to escalate to Venatus for assistance on the bad ad hunt. This particular ad appears to have multiple sources. But! every time a player emails in their report with the bad ad's HAR file, it's a solid lead both on a source and on how widespread the issue is.

If you're still experiencing this ad, definitely follow the instructions laid out on Hiveworks ad reporting page. Your reports are making a difference!

We've removed some comments that were unrelated to the topic of this thread as cross-posting about an issue being discussed in one thread (Thread A) in other, unrelated threads can lead to the current thread (Thread B) being derailed. It can also be considered trolling if review shows the individual posting in Thread B is an active participant in Thread A.

As of this post, the replies removed were done so under forum moderation and Support will not issue any actions or penalties. Thank you.

Hello and good morning! This thread is now locked, under forum moderation.

We are locking the threads regarding the Fathom F Secondary fixes for several reasons. The discussions are slipping out of established threads and into multiple threads on the topic. Not all of the replies being made are constructive and can lead to inflammatory rhetoric and escalation. Comments on the issue are being posted in unrelated threads.

Players had the weekend to post their thoughts publicly in our forums and discuss them with each other. Now it's time for the team to review, confer, and respond, which may take some time. Not because we don't take your concerns and feedback seriously — we have to coordinate around different workflows and schedules while balancing multiple internal and external priorities and needs.

Going forward, we ask that any feedback on the Fathom F Secondary fix or the process for gene releases or fixes in general be submitted directly to us through Contact Us. Your feedback will be documented and reviewed, even if you don't receive a personalized reply.

This means that any additional threads posted about this topic will be locked, and any replies in unrelated threads will be removed, either by Flight Rising Support, myself, or our volunteer moderators.

To everyone who took time to share their feedback constructively, thank you. We appreciate you.

It is I, the bearer of dull news and deflated hype bubbles.

The delay between content updates is due to life lifeing and software being a bit finicky about how it wants to run. Is it ideal, is it what we want? Nope. But sometimes it happens, and then suddenly it's Friday night. We try not to push updates on Fridays and weekends because that's the tech equivalent of saying the 'q' word in healthcare or retail

But! There's a regular content update in the works that we hope to have out to everyone early next week.

Our apologies for the delay in content updates!


@JavaMP

Hey everyone, thank you for your feedback and making your voices heard, especially to those that helped keep the direction of the threads in Flight Rising Discussion and the Suggestions forum constructive. We know your Fathoms and their aesthetics are important to you and that you're feeling concerned or upset over the seeming lack of communication regarding the technical fix we rolled out for Fathom F secondary genes. This was concerning for us, as the fixes were notated and documented in the Fathom Gene Error thread in real time. We've gone over previous gene fixes, what went well, and what happened with the Fathom fixes. We have an update for everyone and information to share on what to expect going forward with gene fixes.


The change:
This was a technical correction, an inconsistency within the same breed. We have defined inconsistencies within the same breed as technical errors since the implementation of the 45 day style consistency window and system we now use for style corrections vs technical corrections. The hatchling pose and the M pose both had the "wrist" of the outside of the wing be the secondary color, and the inside of the wing be the primary color. The F pose originally had the primary showing across the back/outside of the wing, which was inconsistent with how both the hatchling and the m pose coverage presented. Technical errors may be addressed at any time, and as an inconsistency within the same breed, this was one of those fixes.







Communication:
This issue was noted while the Fathom gene error thread and consistency window was open, with notations that it would be addressed after thread closure so that the coverage change was applied on top of any other fixes or changes that were reported within the thread, to avoid duplicating work.


Updates were provided within the thread itself as to the progress of the fixes. The bulk of the Fathom F secondary corrections went in on August 21, 2024, with Clouded, Constellation, Current, and Shimmer outstanding. Clouded, constellation, current, and a fix for an offset on striation went in on October 6th, and Shimmer went in today. These changes were noted within the thread as they were applied.


Going Forward:
Though the thread was being updated, players may not have known to continue to check it for information once the consistency/style fixes were applied and closed out. We should have created a new thread for this fix or moved the updates to it to the modern technical errors thread, as these would have been more logical choices to keep players up-to-date on what was happening.

This was a case of us using a closed release thread past its expiration date. In the future, any technical errors that are corrected past the closure of an initial gene/breed release technical/consistency combo thread will receive their own reply in the stickied, long-term technical errors thread rather than an edit to a closed thread. These new replies will ensure that they show up in the dev tracker and should provide more visibility to the updates that are occurring around the site.

Hey folks, references and links to the account Naomi have been removed. The overall tl;dr for what happened is that a team member mistyped an integer during data entry and it resulted in everything displaying as a single player/dragon.

The reason for the links/reference removal is because this is still a player account and it's a form of call-out that can place unwanted community attention (aka, harassment) on a single account. Thank you for understanding.

Good morning everyone! A quick forum moderation note: A rule-violating reply was removed from the thread. We removed any quotes or replies to removed content under standard issue forum moderation. Thank you!

@clockworkMoose, thank you for your feedback! This is already being discussed and will be given the full attention it deserves.

Hello everyone. Going over the last page of this thread, it's time for a time-out. This action is standard forum moderation and should not be read into as a staff commentary on the thread's topic.

Now, regarding the topic (the Fathom F technical error and corrections), we don't have an update for our players voicing their concerns at this time. That being said, please know that your feedback has been documented and brought to the art team's attention.

Thank you for the report @CoastalSystem

The item name in the database was a little goofy, but it has now been fixed.

Future forum posts/dragon profiles/clan bios/etc. should show the icon as expected. You can also edit existing posts to force them to grab the updated icon.

That would be why I linked and fully quoted the July 2023 comment here. Now it's definitely in the Dev Tracker and it's in the relevant announcement post, as a quick bandage for the time being. Regardless, thank you for the feedback, @clockworkMoose!

@KaijuTamer, our apologies for the confusion — dark mode is definitely on our list to tackle, but it is a significant undertaking for an art-heavy site like ours. I'm going to quote myself from July of 2023 which lays out some of our process on the subject of accessibility and dark modes. (bolding emphasis mine)




A dark theme is something we want to do, but we don't have an ETA at this time. Screenreader accessibility is a critical accessibility issue and one we must address before we can scope out and tackle dark mode and more. I hope this information helps!

Hi @spxcesoul, my response was given in good faith, providing transparency and clarifications for concerns raised by players. There's no benefit in a Community Manager lying to (ie, having intent to deceive) their community.

A concern was raised and that concern was addressed. 'Zaza' is a word and title with multiple valid uses and meanings, and any association to a niche definition in a specific community is wholly unintentional. With this concern addressed, we expect the discussion to return to the overall topic of this thread, the update to Ancient Arboriculture Observations.

The following changes went in tonight:

• Primary: Fern (Aether M) - The belly highlights were extended to the tail.
• Primary: Ground (All Aether) - The horn and claw accent colors were inconsistent with every other instance of this gene, and have been corrected.
• Primary: Python (All Aether) - The accent gradient coverage was brought in line with modern dragons displaying this gene.
• Primary: Tapir (All Aether) - The markings on this gene were thicker than in the modern version of the gene. They have been corrected.
• Primary: Wasp (All Aether) - Additional highlights were added to the furred areas of this gene.
• Secondary: Chess (Aether F, M) - The edge markings have been adjusted again to better flow with the wing.
• Secondary: Striation (All Aether) - The markings on this gene were thicker than in the modern version of the gene. They have been corrected.
• Tertiary: Capsule (All Aether) - The doubled up shadow layer was corrected.
• Tertiary: Firefly (All Aether) - The firefly on the nose was clipping into the standard-eye placement, independent of special eye effects.
• Tertiary: Flameforger (Aether M) - The flames at the end of the wing near the edge of the canvas had their shaping adjusted. Note that this was not a part of the Aether gene expansion, but it was released within a similar timeframe and was still within its 45 day window for consistency changes.
• Tertiary: Koi (Aether F, M) - The gene now applies over the toe pads/beans and is consistent with other breeds that have this gene.
• Tertiary: Veined (All Aether) - The corners on this gene were sharper than on previous breeds. Shaping adjusted.

Based on some of the replies we've seen both here in our forums and on social media, it's important for everyone to note that two things can be true at the same time.

First, that players were right to raise concerns and call our attention to where our story fell into or made space for harmful and racist stereotypes and/or tropes. The concerns raised were/are valid and we had work to do.

Second, that the story and the Auraboa were — in both iterations — informed by lived experience with communication differences. Specifically, living in a world where how you process, interact, and engage with your surroundings is significantly different from those around you and all the misunderstandings, confusion, and pain that can come with those differences. Thank you for seeing them and for the opportunity to address this overall issue, @TheBirdandtheBow.

Neither truth invalidates the other. Discussion of the story, what you liked, what you didn't like, that's all okay. Encouraged, even! What we don't want to see is our community re-litigating the circumstances that lead to the update of Ancient Arboriculture Observations. That will make space for and invite bad faith takes and bigotry. The community brought valid concerns to our attention. We updated the story in response to those concerns and provided insight to our process. And now we're moving forward.

Hi @Farglow! I appreciate your point! The story underwent review by >10 professionals over the past 10 months, and this particular association never came up. In all reviews, it was recognized as a gender neutral parental nickname. Any association as described is wholly unintentional.

After reading your reply, I performed several searches — due diligence, abundance of caution, etc. As you've described it, it appears to be a specific usage based on a product provided by a brand in a specific community. Further searches of just 'Zaza' show that this is also the name of several restaurants, given and surnames of multiple public figures, the name of multiple geographical places, and going by some of our feedback, is a parental reference some our players use for themselves.

All in all, it appears 'Zaza' a widely used name and term with multiple, valid meanings.

(edited to correct the length of time, I miscounted!)