Changes for June 5th, 2019

June 5th, 2019

 

Greetings Beyonders!

 

It's been a while since we've done a changelog for smaller bug fixes / improvements, but we've had some deployed to production recently that we wanted to re-cap so here goes:

 

Fixes:

  • Fixed an issue with unassigned characters not showing in the campaign character listing as soon as they were created.
  • Fixed an issue with additional monster lore data not showing for all applicable users, relative to content sharing.
  • Fixed an issue with user url routes for users registering using Google Auth on mobile. (The fix would apply for all users past that date, and previous users would need nickname credits).
  • Updated the Privacy Policy and Terms of Service links that were 404 on the Google Auth modal.
  • Marking all forums or forum threads as read has been fixed.
  • Correctly copy monster skill bonuses when copying a monster for use as a homebrew template.
  • Fixed an issue with some campaigns showing in the Active and Inactive sections in a user's campaign index.

 

Improvements:

  • A vehicles section has been added to global search and a vehicles filter added on the search results page. Granted, there's not a lot of vehicles at the moment, but I have a feeling that may change in the future.
  • Private messaging is updated so that users you've ignored can no longer send you a private message nor trigger a notification.
  • Feat Options now have the ability to add Actions.

 

Is this really all y'all have been doing?

Certainly not. As Badeye has mentioned before, we have grown from one small team of a couple of developers to three development teams (and are continuing to staff up even more!) focused on various aspects of the product . For example, our "Challenges" team is currently working on the Encounter Builder feature, which is in alpha, while the "Characters" team is working on the mobile app version of the character sheet. 

However, a good portion of the work that we are also doing is what we call "deconstructing the monolith". DDB, as you currently know it, is built on an older code-base that was a carry-over from the early days for Curse, Inc. The growth that DDB has experienced has necessitated us migrating out of that older, monolithic, paradigm to an architecture that is more flexible and more scale-able.

Our three engineering teams balance working on product features (what our customers need) with engineering needs. Engineering things that we've done recently, which customers don't see, include building and launching a distributed authentication system, a distributed entitlements system, and a distributed vehicle service. A successful launch of these systems entails our customers never noticing a difference in how the product operates, and provides the foundation for "deconstructing the monolith". 

As we're able to start pulling the pieces of the monolith apart, you will see more rapid updates on products as we gain the ability to implement changes that are smaller in scope. Our goal is to achieve a state of continuous integration and continuous deployment. Meaning, our changes are continually getting deployed and there is little to no development work-in-progress (WIP). We're not there yet, but we've got a motivated, dedicated, and excited group making great progress towards this goal.

We are continually thrilled with all of the support, feedback, and constructive criticisms, that you, our users, provide. You help us more than you know!

 

Happy dragon slaying! (unless you're a dragon, then happy, um ,well, TPKing characters?)

 

25

Comments

  • To post a comment, please or register a new account.
Posts Quoted:
Reply
Clear All Quotes