CurseForge Comms for Apr 7th, 2017

Greetings and salutations, Authors!


As many of you may have noticed recently, many things have been changing in the last 6 months for Curse. We know there are plenty of questions, concerns, and issues that have been brought to our attention.


The team has been wanting to develop a more clear communication pipeline between our development team and the communities for quite some time. Due to lack of resources and staff, this hasn’t been something we have had any way of effectively carrying out. Not to mention, many things we were working on we just could not discuss for logistical and business reasons.


Which brings me straight to the point of this article...


Starting today, and continuing semi-monthly (maybe more!), we’ll be putting together a post consolidating all of the changes, fixes, features, etc that we’ve completed or are working on. Some weeks will have a lot of things, some weeks won’t. Either way, we’re going to do what we can to communicate with you the things we feel you would want to know.


This won’t always just be a changelog, but will also include information about events we’re attending, places we’re going to be, cool things we want to share with you guys and in general a more open and honest window into the week to week here at CurseForge.


This first round up is very WoW heavy - but we’re doing our best to balance out the work so future updates will be a bit more diverse! So without further ado, here’s a list of the most recent fixes!


Fixed and released:

  • Found a missing digit for @packager-date-integer (WoW)
  • Tags no longer spit out exclusively Alphas from Mercurial repo (WoW)
  • Localization will no longer duplicate itself when deleting (WoW)
  • An “Unhandled Exception” in the WoW Packager has been handled, preventing files from incorrectly being flagged as complete prematurely (WoW)
  • WoW Packager now correctly outputs UTF-8 encoding in changelogs (WoW)
  • SVN Packager no longer repackages the latest tag for every commit. (WoW)
  • Packager now realizes when repos have changed their type (WoW)
  • Packager has gone to school and names Alphas a bit more clearly (WoW)
  • When exporting tables, quotes are no longer trimmed off the end (WoW)
  • You can now import and export localizations via API (WoW)
  • Fixed edge cases where syncer would not sync projects to client (WoW)
  • Block downloads on files until they are fully processed (WoW)
  • Translations “Needs Review” checkbox now defaults to true (WoW)
  • You can now delete localizations without the website complaining (WoW)
  • Localizations managers can now manage localizations (yea I know) (WoW)
  • Localizations no longer freak out when editing their namespaces (WoW)
  • Fixed crash when importing translations with “Delete if no Translations” selected (WoW)
  • Rewrote Maven handler to adhere closer to Maven standards (Minecraft)
  • Removed API requirement from Maven (Minecraft)
  • World of Tanks now supports .wotmod uploads (WoT)
  • Changelogs have been cut in half or more (no longer duplicating) (Various)
  • Added “Thanks” to appropriate communities for better  user interaction. (Various)
  • Trying to access a project on the wrong site will now redirect you to the correct site (All)
  • Users can no longer see tickets marked as SPAM (you’re welcome) (All)
  • Trying to access a project by it’s ID will correctly redirect to the project (All)
  • Filters on project listings will now remember your last settings across sessions (per site) (All)
  • Uploading images will now correctly re-submit your project for moderation if required (All)
  • Issues now have default template options (All)
  • Issue managers can now properly manage issue settings such as Tags (All)
  • Fixed crash in Project Pages (x3, yep there were multiples) (All)
  • Replies now reply accordingly in comments and forum threads (All)
  • General speed improvements (SQL indexes added to reduce query times) (All)

Eventually, we hope the fix list is relatively short. Not because we will ever stop fixing bugs, but because we hope we don’t create them faster than we fix them! But these posts aren’t just about what we’ve done, it’s also about what we’re doing. In addition to these fixes, we also have updates that will be going live in next week's release:


Things in QA (Fixes coming soon!)

  • File uploads to WoWAce blocked correctly (WoW)
  • If your file does not need Localizations the original file will be served to the users (WoW)
  • Action Logs for the Packager! Now with more info! (If it fails, we’ll try to provide info on why) (WoW)
  • You can now change your project name and slug independently (HOORAY!!) (All)
  • File Details page now shows upload date (All)
  • Hashtags no longer break the everything (handled correctly in download links) (All)
  • Tag deletion now removes the tag from associated issues (All)
  • File uploads to Abandoned or Inactive projects will now re-activate those projects (All)
  • Changing slugs temporarily preserves old slug as a redirect to new slug (All)

Lastly, I want to talk a little about the future of CurseForge. I know with all of the changes there are quite a few concerns about Author Rewards, CurseForge as a business, the state of individual communities, and much much more.


First and foremost, the team here at CurseForge is 100% committed to CurseForge. In fact, we’ve organized ourselves as a proper division within the company, and as a team we have chosen to double down on our core ideals, motivations, and passion for what these sites are. In the last several weeks, as we’ve met and planned, I’ve seen renewed passion and excitement from the entire team.


We’re not going anywhere!


As for other concerns, there will be further announcements and info regarding most if not all of the major points in the coming weeks. We will be absolutely sure to let you know right here, from this point forward, any time there is important news regarding CurseForge.


Wow! This is a long one, but I wanted to make sure I was clear and thorough. Now, what I need from you guys is feedback. Give us whatever you’ve got down below. The only thing I ask is that you keep it constructive. Many of you who have come across me in forums and comment threads know that I’m happy to take constructive criticism, even if it’s harsh - but rude, non constructive, or disrespectful comments are still not appropriate and may be removed.


Keep it clear for real issues, comments, and discussion so that we can easily pick those up, track them, and get them into our tracker.


That vast majority of those who I’ve spoken to, even the most outspoken of the communities, are driven by passion. That’s something that no matter how harsh it comes across, we will take with open arms.


Thanks for reading!

Your friendly neighborhood MrFlamegoat



Posts Quoted:
Clear All Quotes