Thanks to @jogerj and @PrimeCicada for the method! Original script: https://gist.github.com/jogerj/0339e61a92e0de2e360c5212a94854e8

Thanks to @SleepingPanda for 3.8 change info

Open powershell, then copy paste this script:

Configurar Nombre que salen en los commits

	git config --global user.name "dasdo"

Configurar Email

	git config --global user.email [email protected]

See how a minor change to your commit message style can make you a better programmer.

Format: <type>(<scope>): <subject>

<scope> is optional

This page has been updated a lot in the past 3 years. Older revisions you might like more than this one:

• June 2021 - list of endpoints for other sports/leagues (i.e. nba, nhl, mlb)
• August 2021 - get historical fantasy league data
• September 2021 - list of endpoints in plain text
• May 2023 - collapsed endpoint response examples
• Mar 2025 - endpoint

WARNING: Article moved to separate repo to allow users contributions: https://github.com/raysan5/custom_game_engines

A couple of weeks ago I played (and finished) A Plague Tale, a game by Asobo Studio. I was really captivated by the game, not only by the beautiful graphics but also by the story and the locations in the game. I decided to investigate a bit about the game tech and I was surprised to see it was developed with a custom engine by a relatively small studio. I know there are some companies using custom engines but it's very difficult to find a detailed market study with that kind of information curated and updated. So this article.

Nowadays lots of companies choose engines like [Unreal](https:

• Site: https://graphite.dev
• Docs: https://docs.graphite.dev/

• Stacked PRs allow you to easily work like so:
  • Work on branch ACQ-000-part-A (which is based on master)
  • Work on branch ACQ-000-part-B (which is based on part-A)

A project created by NPC on LiveCodes.

Your org's brain that AI can use

This document describes the conceptual architecture of the Inferal Workspace - a text-based, version-controlled knowledge and operations hub designed to replace tools like Notion and Webflow while being natively accessible to AI assistants.

As an engineering-driven organization, we found ourselves fighting our tools instead of using them. Notion couldn't keep up with how we actually work - context scattered across pages, no version control, and AI that could read but not act. Webflow meant our website lived in a silo, disconnected from our codebase and deployment pipelines. Every tool was another tab, another context switch, another place where knowledge went to die.