TTT2 icon indicating copy to clipboard operation
TTT2 copied to clipboard

fix buy menu error #skip-changelog

Open EntranceJew opened this issue 6 months ago • 2 comments

it's gotta go someway somehow

EntranceJew avatar Feb 11 '24 23:02 EntranceJew

this fixes #1403 btw, something that should happen prior to v0.13.0b

EntranceJew avatar Feb 12 '24 00:02 EntranceJew

@saibotk What is your opnion on that? I don't care that much. It is the easiest fix to that problem.

TimGoll avatar Feb 12 '24 06:02 TimGoll

Closed in favor of #1421

saibotk avatar Feb 18 '24 10:02 saibotk

Closed in favor of #1421

I don't think #1421 is fixing the issue that exists here. @ZenBre4ker should comment on that, but I'm pretty sure these are different issues

TimGoll avatar Feb 18 '24 10:02 TimGoll

Well, it seems like this was the idea to make unarmed being editable, but I also don't know how to reproduce #1403 to confirm, that it fixes anything. This just allows it being shown in the shopeditor, right?

ZenBre4ker avatar Feb 18 '24 10:02 ZenBre4ker

Yes. But the problem here is, that the material is only cached if it isn't ejected. If the material isn't cached, it throws an error at a later point. I didn't try to reproduce the issue though, but this is the issue that exists here.

TimGoll avatar Feb 18 '24 10:02 TimGoll

Still seems wrong to not eject it in the equipmentForRoleAll. If caching is somehow important, it should be done somewhere else entirely. Weird enough, that those two calls are entangled: ShopEditor.GetEquipmentForRoleAll() and hook.run("TTT2RegisterWeaponID")

That is something I probably was on the way to untangle, but that was maybe inside one of those PRs that a took a long to get reviewed.

ZenBre4ker avatar Feb 18 '24 11:02 ZenBre4ker

yes, it is bad that these are entangled! This is why the fix in this PR is more a bandaid fix then a real fix. I just wanted to point out that your PR does not fix the issue at hand.

TimGoll avatar Feb 18 '24 11:02 TimGoll

Oh then nvm i was wrong but will keep this closed as we need a fix that does not just allow this to be editable

saibotk avatar Feb 18 '24 11:02 saibotk

THE PROBLEM IS THAT EVERY TIME YOU OPEN THE BUY MENU IT ERRORS

EntranceJew avatar Feb 18 '24 17:02 EntranceJew

ERRORING EVERY TIME YOU OPEN THE MENU SUCKS

EntranceJew avatar Feb 18 '24 17:02 EntranceJew

Please keep the discussion civil and on topic. We are aware of the issue, but we want a fix, not a bandaid. Therefor this PR is not a good solution to us. This is nothing against you, this is only about this project as we told you on discord before you opened this PR.

TimGoll avatar Feb 18 '24 18:02 TimGoll

"this should be done better" with no indication of what better means is the opposite of useful, it destroys labor

EntranceJew avatar Feb 18 '24 18:02 EntranceJew

"this should be done better" with no indication of what better means is the opposite of useful, it destroys labor

I'm not here to discuss with you. As we just wrote here and explained on discord, the whole caching and registering system has to be changed so that this won't happen anymore.

TimGoll avatar Feb 18 '24 18:02 TimGoll