lag1

Privateunrated

Content

20 lines
{delete} 
{=(em):<:AL:809445888836501594>}
{=(em1):<:AL2:809449171001278485>}
{=(em2):<:tarr:833359411158319134>}
   
{=(title1):{em}**__Got lag? Maybe we can help.__**{em}}

{=(desc1):**```
These tips were all developed based off my own personal experience with Windows 10. If anyone here uses Mac and is able to see if any of these can be translated for Mac please DM me so we can make a Mac tailored channel as well.
```**}

{=(title2):{em1}**__BASIC INFO__**{em1}}

{=(desc2):**{em2}If you want to know if your problem is FPS vs ping just hit the backtick key (one key left of the #1 key) while you're in lair or in a game. You'll see a tiny box pop up in the upper left corner. Look at the FPS and the first number of the ping. You can keep it on while you play to see the live stats. Pressing the backtick key again will toggle it off.

{em2}Generally (there are some exceptions based on your hardware) your FPS should be around 60, potentially with some slight drops during big kills, etc. Jerky visuals and stuttering are often caused by low FPS. Anything consistently under 50 FPS will be fairly noticeable. 

{em2}For ping, obviously the lower the number the better. I'd consider anything under 100 to be very easily playable, however many people will begin to notice lag around 80+. High ping is what causes delay lag where it feels like you're swimming through wet cement.

{em2}The most important thing with both FPS and ping is a somewhat consistent number. If Chicago is listing a ping of 65 ms in the server selection then I would hope to see that number stay around 50-80 or so while I'm playing. Larger changes will have a significant impact. Unstable ping is way worse to play with than a consistent, stable higher ping.**}

Embed

1 line
{"color": 5198940, "title": "{title1}", "description": "{desc1}\n{title2}\n\n{desc2}"}
Raw JSON
{
  "id": 782288,
  "created_at": "2021-04-27T00:48:17.000Z",
  "tag_name": "lag1",
  "nsfw": false,
  "owner_id": "650362174501552134",
  "uses": 7,
  "description": null,
  "restricted": false,
  "shared": false,
  "deleted": false,
  "safe": "unrated",
  "hidden": false,
  "guild_id": "657692633283559436",
  "sharer": "650362174501552134",
  "content": "{delete} \n{=(em):<:AL:809445888836501594>}\n{=(em1):<:AL2:809449171001278485>}\n{=(em2):<:tarr:833359411158319134>}\n   \n{=(title1):{em}**__Got lag? Maybe we can help.__**{em}}\n\n{=(desc1):**```\nThese tips were all developed based off my own personal experience with Windows 10. If anyone here uses Mac and is able to see if any of these can be translated for Mac please DM me so we can make a Mac tailored channel as well.\n```**}\n\n{=(title2):{em1}**__BASIC INFO__**{em1}}\n\n{=(desc2):**{em2}If you want to know if your problem is FPS vs ping just hit the backtick key (one key left of the #1 key) while you're in lair or in a game. You'll see a tiny box pop up in the upper left corner. Look at the FPS and the first number of the ping. You can keep it on while you play to see the live stats. Pressing the backtick key again will toggle it off.\n\n{em2}Generally (there are some exceptions based on your hardware) your FPS should be around 60, potentially with some slight drops during big kills, etc. Jerky visuals and stuttering are often caused by low FPS. Anything consistently under 50 FPS will be fairly noticeable. \n\n{em2}For ping, obviously the lower the number the better. I'd consider anything under 100 to be very easily playable, however many people will begin to notice lag around 80+. High ping is what causes delay lag where it feels like you're swimming through wet cement.\n\n{em2}The most important thing with both FPS and ping is a somewhat consistent number. If Chicago is listing a ping of 65 ms in the server selection then I would hope to see that number stay around 50-80 or so while I'm playing. Larger changes will have a significant impact. Unstable ping is way worse to play with than a consistent, stable higher ping.**}",
  "embed": "{\"color\": 5198940, \"title\": \"{title1}\", \"description\": \"{desc1}\\n{title2}\\n\\n{desc2}\"}",
  "last_fetched": "2026-10-21T01:16:18.683Z"
}