Talk:Conditional Out of Bounds
Two conflicting codes for the same thing
I am already talking to Riidefi and Kevin over Discord, but I think this is better suited here.
Both Riidefi and Kevin released a "conditional OOB" code today/yesterday, probably mainly for the track CTR N. Gin Labs. Now, sadly, both of these codes are completely incompatible with one another, since they use the parameters differently. Given that the point of these codes is to become widespread, and eventually get implemented into distributions like CTGP and LE-CODE distributions so that tracks can take advantage of that, I think that that is a bad idea.
There are now two competing cheat codes, for the same thing, and A) distribution creators can only support one of them, and B) track creators can only support one of them either. I think the unofficial update for [CTR N. Gin Labs]] made by Riidefi (which apparently the author of that track doesn't like in its current form and didn't give permission for) was a bad idea, while there are two conflicing cheat codes, and both of them are still being tested and updated.
Now I know that I can't force anyone to do anything, but I'd say that making a cheat code for a custom feature, then releasing a track update that requires that particular feature, with the author NOT liking the implementation of that particular feature (as I've been told by Kevin) is a bad idea.
I would recommend removing the unofficial 1.3 update from the CTR N. Gin Labs page again (if the author aggrees), then for Kevin and Riidefi and potentially others from the community to come to a conclusion about which of the two cheat code variants would be better suited for that case, and then having ONE type of conditional OOB code in the Wiki and update the track to work with that one.
The current situation (two different cheat codes, incompatible with another, no distribution can use both, no track can support both) is only going to cause trouble in the future.