Jump to content

Number Six

Homecoming Team
  • Content Count

  • Joined

  • Last visited

Community Reputation

141 Excellent


About Number Six

  • Birthday 01/01/1004
  1. Removed the hard limit, and the soft limit. MAX_COSTUME_PARTS is gone, so unlimited lag costume parts here we come! In all seriousness, the first application of this tech will probably be something boring like fixing the customizable weapon slots that conflict with customizable epic pool weapons. That was the primary motivation for removing all the hardcoded limits to begin with; extra auras are just a bonus. Then maybe separate path auras out. I also have some ideas for how to do things like eye/hand auras in a sane way to allow them to be set independently without overloading the costume UI, but that's a bit further off because it involves reworking the costume creator a bit, and the way I'm thinking about doing it actually wouldn't have required expanding the part limit.
  2. Yeah, a whole month is too much I think. We have some ideas for next year to make the event more dynamic and less of a drag, while still providing a large window of opportunity for players who can't log in every day to participate.
  3. Minor font rendering differences are probably a result of upgrading the FreeType library the game uses from some ancient version that was last updated right around never ago to the current version. But that wasn't in this patch, it's been out since at least the one prior to it. IIRC FreeType changed at some point to autohint (snap to pixel boundaries) vertically but not horizontally, similar to ClearType and other technologies that take advantage of subpixel rendering.
  4. That’s something @Cipher was working on... he showed me a prototype of an HSL picker a couple months ago. There’s a few niceties we would want in such a tool, such as remembering color swatches already used in the costume for easy matching. The UI code is a bit of a pain to work with so I think it got backburnered while we deal with some other things that need attention. But I’m sure it’ll come back to the forefront at some point.
  5. Certainly doable. I was playing around the other night and did this as a silly proof of concept. Took a few hours because I had to rework the database schema to remove the hard limit on 30 costume pieces and fix the absolutely awful way they were stored in the database, but now we can add as many as we want so that opens up a lot of options. As you can see taking things too far makes the UI a little... difficult to see... so some careful thought will have to be placed into the best way to have maximum flexibility and still have it be usable. Maybe splitting off path auras into a separate slot for starters. Ideas are welcome.
  6. The link you posted is for the Visual Studio 2010 runtime, which is an older one that won't work. We're using VS2017, so you need the first download on this page: https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads Make sure to download the 64-bit (x64) version.
  7. Also wanted to try to avoid confirmation bias in people reporting whether or not it helped with the crash issue, but okay, point taken. Edit: There, done. 😉
  8. It would quite literally be the “bug fixes and performance improvements” patch note that everybody hates on mobile apps. The only change is a minor adjustment to particle physics to try to prevent the crash to desktop issues a number of people are experiencing. But since we don’t have any good method of reproducing the crash, it may not actually fix the issue. So... no visible changes = no patch notes.
  9. The pre-ED values are useful for knowing how much enhancement value is being wasted and can tell you if you've overslotted a particular attribute.
  10. If there is anyone who is consistently experiencing this crash, is comfortable enough with file management to drop in a test client, and is willing to help us out by submitting crash dumps, please shoot me a PM.
  11. Not currently, but we have something nearly ready for this that is just waiting on the updated privacy policy that covers crash dump data. So... soon, and not the trademarked variety.
  12. Tequila doesn't need to, and if someone wants to put together a band-aid for that particular issue and submit it as a PR on GitHub, it would likely be accepted. Tequila isn't something we developed, it's just something we happen to be using at the moment. As for whether or not we should redirect any of Homecoming's resources to fixing that particular issue, that's an open question. It's certainly doable and may end up being a quick fix, but given the number of other issues with Tequila and the fact that we'd like to dump it in favor of something more robust anyway, it's a question whether dealing with the logistics of rolling out a new version is worth spending time on.
  13. The draft spec I've been working on for the next-generation manifest does not include the capability to touch files outside of the base directory of the package in question. I believe Island Rum has some legitimate use for that as it also handles installing wine and some other housekeeping necessary for the Mac version. For that it may require creating some extra packages with a more expansive scope to handle it, but we're not to the point of looking at it just yet.
  14. The issue that was brought up isn't really a 'vulnerability' per se, it's simply the nature of automatic downloaders. If you are trusting a program to automatically download updated executables, those executables can do anything they want to your system, including downloading malware. There is an implicit trust in any manifest you add to something like Tequila, and users should be fully aware of just what they're signing up for. tl;dr: if you're worried about somebody putting absolute paths in a manifest file to overwrite files in system32, you should also be worried about what the exes they're downloading and running can do. We have always recommended running the various downloaders as non-privileged users (do not use "run as Administrator"). That mitigates the damage to the OS that can be done, but even non-privileged programs can access data files which are what most people care about. It does not appear that this new patcher addresses the real weakness in all of the updaters available to date -- the possibility of man-in-the-middle attacks or DNS hijacking. That's something that we've been concerned about for some time. Due to that, as well as Tequila being generally lacking in other features that we would like to have, the team's consensus has been to consider it a temporary utility until the new community patcher (Sunrise) was finished. Unfortunately Sunrise development seems to have stalled as far as I can tell. We had some plans for our own updater in the future that we had been holding back on to avoid duplicating effort, but those will likely move up in the priority list.
  15. It was just a reversion of the font rendering library upgrade that had not undergone any QA testing and shouldn't have been part of the original patch. Otherwise identical.
  • Create New...