Keyoverlay showing wrong values on Linux

[hwsmm]

Hi, I've been writing memory reader of mine in another language, and I just found out that

gosumemory/memory/functions.go

Lines 51 to 55 in f80a655

	if UnderWine == true || runtime.GOOS != "windows" { //Arrays start at 0xC in Linux for some reason, has to be wine specific
	leaderStart = 0xC
	} else {
	leaderStart = 0x8
	}

applies the same to these lines. (0xC instead of 0x8)

gosumemory/memory/functions.go

Lines 433 to 442 in f80a655

	var entries struct {
	K1Pressed int8 `mem:"[Base + 0x8] + 0x1C"` //Pressed usually works with <20 update rate. It's recommended to create a buffer and predict presses by count to save CPU overhead
	K1Count int32 `mem:"[Base + 0x8] + 0x14"`
	K2Pressed int8 `mem:"[Base + 0xC] + 0x1C"`
	K2Count int32 `mem:"[Base + 0xC] + 0x14"`
	M1Pressed int8 `mem:"[Base + 0x10] + 0x1C"`
	M1Count int32 `mem:"[Base + 0x10] + 0x14"`
	M2Pressed int8 `mem:"[Base + 0x14] + 0x1C"`
	M2Count int32 `mem:"[Base + 0x14] + 0x14"`
	}

---

I'd write a PR if I were good enough at Go, but unfortunately I couldn't come up with a good solution, so I am just writing an issue.

[C0D3-M4513R]

So you are saying, that K1Pressed should be the same as K2Pressed?
And K1Count should be the same as K2Count=? seems broken...

[KotRikD]

It's not the same thing. It just pointers to start of array with values. LeaderStart is needed to calculate current value pointer in array (NOT START OF ARRAY)