Skip to content

Instantly share code, notes, and snippets.

View Magoninho's full-sized avatar
:octocat:
studying

João Felipe Ribeiro Magoninho

:octocat:
studying
83 followers · 54 following
View GitHub Profile
@JerryLokjianming
JerryLokjianming / Crack Sublime Text Windows and Linux.md
Last active May 6, 2025 12:26
Crack Sublime Text 3.2.2 Build 3211 and Sublime Text 4 Alpha 4098 with Hex

How to Crack Sublime Text 3.2.2 Build 3211 with Hex Editor (Windows | Without License) ↓

  1. Download & Install Sublime Text 3.2.2 Build 3211
  2. Visit https://hexed.it/
  3. Open file select sublime_text.exe
  4. Offset 0x8545: Original 84 -> 85
  5. Offset 0x08FF19: Original 75 -> EB
  6. Offset 0x1932C7: Original 75 -> 74 (remove UNREGISTERED in title bar, so no need to use a license)
@mrspeaker
mrspeaker / pseudo-code.java
Created March 5, 2012 13:56
Why does Notch check X and Y separately in the collision detection routine?
/*
After watching a few of Notch's (and Mojan's) "write a game in a weekend" livecasts and
pulling apart some of the code (http://www.mrspeaker.net/2011/12/30/colorising-sprites-1/)
I've noticed that the collision detection routines are broken into two methods - usually
called "move" and "move2".
The move method gets the amount the entity will move on the X axis and calls
move2 with move2(x, 0). Then the same thing is done with the Y: move2(0,y).
Why would this be necessary? I've broken the code down into pseudo code to see if I