MakeLobbiesGreatAgain Versions Save

Steam Networked-based Game Lag Checker

2.2

5 years ago

Required updated due to removal of Kindred and the number of people still hitting the server for requests

OOPSIE WOOPSIE!! Uwu We made a fucky wucky!! A wittle fucko boingo! The code monkeys at our headquarters worked VEWY HAWD to fix this!

  • I broke Blocked/Loved with the last version, because I merged the removed version and didn't notice. Should be working properly now.

2.1

5 years ago

Block/Love bind is currently broken due to a mistake. Will be resolved later.

Use 1.39 for now.**

  • Brought back the block feature
  • Removed log functionality - This removes grabbing SteamIDs from the one game's logs to prevent duplicate information. Really, there is better ways to do this that is fairly generic, they just need to be implemented later.
  • Removed backup functionality - Not needed for that particular game anymore anyways.
  • Stripped out Kindred - The reason for this is mostly that as time went on it was only hitting about a 15% hit rate on average for letting someone else know that a person had a different IP. This isn't so much an accuracy issue but that fact that players still using it see a lot of the same people repeatedly. There is a pool of about ~211k unique players recorded and that steadily stopped increasing, even with people still using MLGA.

What all this means is that blocking is back to being entirely IP-Hash based. The file may grow a bit bigger (due to duplicating a person's IPs). Other than that, accuracy shouldn't really be affected as most countries have ISP that retain your IP for extended periods of time based on your modem MAC address, so people won't be constantly avoiding being blocked by you.

At a later date, I'll hopefully add some more accurate functionality the will prevent the IP-Hash from even being needed.

1.40

6 years ago

From this point forward, MLGA is no longer branded with Dead By Daylight or related imagery, nor will I provide support regarding the game. The developers have expressed their distaste for a block feature while not providing a fix for the core issues that make users desire one.

Backup and block related features will be stripped from the core application. Blocks will return when they are no longer tied to game-specific functionality.

Nothing will be put in place to prevent its use with the game as a ping indicator and a fork will likely come along to continue the normal functionality, as this program has a permissive license to do so. The program, regardless of who is writing it, it is now operating under a "Use at your own risk" policy.

You can click the number next to Fork in the top right to see those that may be continuing with previous state of MLGA.

BUP-1.0

6 years ago

For those of you who wanted the Backup system now that the game has an in-game ping indicator, here ya go.

If you don't see the Jake icon show up in your tray or it doesn't stick around when moused over, you may need to grab JRE 9 from here: http://www.oracle.com/technetwork/java/javase/downloads/jre9-downloads-3848532.html

1.39

6 years ago

This update is Required due to bug fixes

  • Fixed some edge cases that would prevent data submission to KINDRED
  • Optimized/Rewrote most of the code to be very Java 8
  • Fixed logic that would cause unnecessary CPU usage

1.0-LJP&B

6 years ago

This is a version that's what it says, just ping and backups. No enhancements, no blocking.

1.38

6 years ago

This update is Required due to the bug fixes

  • Fixed a major bug that somehow didn't break the Overlay's remove function after you've been disconnected from someone for a while
  • Fixed Issue #68 / #69 by addressing the actual issue, which turned out to be a log that ended abruptly due to a DbD crash or something
  • Increased timeout on session connections before removing them from the Overlay by setting the time to 5 seconds instead of 3.5, so that you have a bit more time to block them. This was mostly to address a particular asshole that pulled their ethernet cord when we got all 5 gens and they hadn't downed anyone.
  • A logic change that will decrease the log parsing time by 0.0000000001 seconds.
  • Everything else was general code cleanup and fixing some typos in logging

Also, from the previous release:

  • KINDRED is a new system that lookups player IDs from a server hosted by ShadowMoose.
    • This opt-in system means you should have the correct player every time you join them, regardless of if they changed IPs, as long as other players are contributing.
    • In order for this to work, you'll optionally need to sign in with a Reddit, Github, or GMail account. This is simply to get an OAuth token to authenticate your requests.
    • This is not a global block list. Your block list is stored locally, and we don't want it.

1.37

6 years ago
  • KINDRED is a new system that lookups player IDs from a server hosted by ShadowMoose.
    • This opt-in system means you should have the correct player every time you join them, regardless of if they changed IPs, as long as other players are contributing.
    • In order for this to work, you'll need to sign in with a Reddit, Github, or GMail account. This is simply to get an OAuth token to authenticate your requests.
  • Added some additional failsafes for missing files, such as Issue #68

For clarification on the system, here's a copy-paste of my post from Reddit.

I'm not providing information about the player with this opt-in database. It's literally been using this information for several versions, but it was only based on people you had played against. And the way it worked was if someone did change IPs, we wouldn't have a Peers.mlga file with 100s of entries for the same guy and you would still have to face the guy at least once, or join the lobby and dodge.

It has nothing to do with storing who is and isn't blocked, that's still entirely a local file. We aren't even tracking that. Our data is literally: their player UID, the hashed IPs they've been seen with, and how many different keys have submitted that the player with that UID is that hashed IP. By opting in, you don't submit your own information currently, that's something that could be changed simply to make the information as accurate as possible for everyone.

By crowd-sourcing that information, there should never be a chance for you to play against someone you'd already blocked. If the developers say, "Hey, we don't want that." Then, I can concede with something like, we'll wipe the database every season so that people have a second chance.

http://i.imgur.com/r5Dir2T.png is what our data analytics look like. The keys are just a number tied to each registered account, and user reports just supply the UID and the number of unique keys that have reported that UID.

For the folks concerned this could someday become a global block list, that's stupid. If I provided that I would be on it, and everyone else would end up on it. There's literally no upside to such a scenario.

1.36

6 years ago
  • Corrected checking on the file size to prevent unnecessary warnings about possible save file loss

This is a fix for Issue #66 and is not necessary for anyone not experiencing that nag.

The KINDRED system is getting close to completion, which will allow folks to opt-in to a system through Reddit, GitHub, and Google accounts, simply by getting an OAuth token for data verification and improved IP lookups.

1.35

6 years ago
  • Fixed the peers.mlga file not being properly closed. This would cause corruption like Issue #63

This update will be Required as it is capable of affecting every user.