[1.12] Light Suppression

I have amended the description, I hope it's fairer now.

Sorry for troubling you with this

Horrible cascading chunk loading ig. The correct solution would be to defer the light update.

@Earthcomputer Yeah, although that would then become vulnerable to restarts, similar to 1.14+ light suppression

@vktec You could save the pending light updates, like with tile ticks

Pog heyo rich

literal

AMAZED RICH
AMAZED RICH

Ey ey ey aaaa quiel rich

Rich para cuando el tutorial de como conseguir bedrock en survival :)

Do you have a link to her video? I asked her for one and she said she didn't have one.

She has none afaik since she didnt care about it much when it was discovered afaik

@Earthcomputer I don't have that link/seen that video, but if you also don't have it then I'd replace "1.14+ light suppression by Kayleigh:" with something like "Kayleigh didn't make it into a video nvm" in your video description

@Sander Bos I never said that Kayleigh made a video

@Earthcomputer I know, but I just meant that in your video's description you have "1.14+ light suppression by Kayleigh:" without anything after the colon, which implies that something was supposed to be linked there. Nevermind, I see how it just introduces the other two links now. :)

and 1.16 feels like spanish, because it's not even about programing

Pallete corruption bro it got me crazy

No light updates get processed within 17 blocks of an unloaded chunk. If you move closer to the portal then light updates can be processed in the area.

there are public deofuscation maps you can use to decompile the code.

For 1.12 I use the carpetmod112 repository, which can be found on https://github.com/gnembon/carpetmod112. Follow the instructions in the readme and you'll be able to do it too :)

Not really, no. The random number generator is literally just 3 mathematical operations, which would likely be more efficient and less error prone than the conditional jump probably required for a counter.

@Earthcomputer I see, thanks. Thought the java RNG was a bit more complex than that.

@Jonah Hertzman mmmm not really

Was the new nether not enough for you

Raid Farms

@nnnik in 1.12: vanilla performance, decent chunk loading, rng manip and much more

@angarn My comment did not try to state that there is more or less features between the versions but rather state that there are unique features in 1.16 that are depending on who you ask interesting

@nnnik yep, fair enough

Ask in #ask-for-help in Scicraft's discord you may or may not get answer

It is updated, what are you on about?

@Earthcomputer How can you use the fihing RNG?

@Megaminx Ik lot it was a joke :)

There are portal farms in 1.12, the caching system is workable, you just have to be smart about it.

I remember that i have seen a video about degg breaking block preserves light, i think people at that time considered it to be a degg thing, but actually it's a just it being nearby unloaded chunks

@Fallen_Breath thats hilarious. also hilariously simple

Lol, that's quite funny

When I feel like it

@Earthcomputer alright, imma be waiting👌

Yeah he does sound exactly like him

Light suppression was figured out in 1.14 and above first, as for other discoveries the older version has been out longer an is generally still played in by technical folks. That gives more time for discoveries to be made.

Nathan Clark Wasn’t sure if it’s just a time thing. If so that’s great, but slightly unfortunate that I’ll always be playing in the version too new for game-breaking discoveries to have a personal impact on the way I play

The main thing is that 1.12 is a relatively lag friendly version and has relatively many cool unintentional features (iron farms, RNG manipulation etc.) which got removed in 1.13 and above. 1.12 is about twice as good for performance as 1.13 is and it just slightly improved to 1.16. Since there is very little new content in these versions to mess around with many servers like Prototech or Scicraft or Hypnos stayed in 1.12 with no intentions of updating, so the smartest tech players which have been around the longest play in that version. That means that they try to break 1.12 a lot more than future versions which leads to stuff like 1.12 bedrock item or 1.12 barrier block.

Lukas Staar Thanks for the reply, I can imagine how it would help having the general lag at a minimum. Also I can’t help thinking that there may be similar-tier glitches waiting to be found on new versions. I am not a code digger though, and am pretty clueless. I guess I just wish more ‘code investigation’ was done on current, relevant versions.

I think it's because much of the more complex tech has other major subproblems which have already been solved. This for example uses RNG manipulation as a subproblem, other things may use savestating or population manipulation as subproblems, or multiple at the same time. Usually when complex tech gets broken, it's down to one or more of just a few things (e.g. population manipulation) that it relied on getting broken. There hasn't been enough time to develop a new "toolbox" of useful bugs in newer versions to be able to use as solved subproblems of a feature we want to achieve.

There is also I think the problem that the tech community has turned too much to modding to solve their problems than continuing to find and exploit bugs to do the same. Some may disagree, but I think this has stifled innovation a bit and made there less incentive to find such bugs which is slowing progress. People also try too hard to look for bugs that are similar to those that existed in 1.12, which in many cases may not exist, and should instead be trying to come up with different solutions entirely. That said, it is hard to "look for" bugs, things often happen the other way around, you find them while looking for other things.

As for myself, I spend much of my code digging time in 1.12, mostly because I don't feel like I am done with the version. I am a modder as well, so I'm familiar with 1.16 code, but I'm reading it in a different way, and don't often come across bugs that are exploitable in tech mc.

@Earthcomputer "Turned too much to modding? I have no idea what you mean..." spawns in bot players instead of building chunk loaders

@Nathan Clark Can't build a chunkloader in the End

@IcyFrost Can't place water in the Nether either. Does that mean one should either A: Install a mod that changes the game to allow water in the nether or
B: Don't build water based farms in a dimension that doesn't allow it

The dimensional restrictions are a part of the game IMO and figuring out how to get around them is all part of the fun of technical play for some.

@Nathan Clark there is objectively no way to get around these restrictions. There is no reason for one to require a water based farm in the Nether; this dimensional restriction is far less significant than the necessity of having an End chunk loader which is required if one wishes to operate any farm or machine in the End.

@IcyFrost Or you just build manual or afkable farms in the End and use them that way. If you want a chunk loaded farm in an empty space there are multiple world eater designs and two other dimensions to choose from.

Hello

Hello

Hello

Hello

Hello

Hello

Hello

Hello

Hello

Hello

Hello

Hello

Hello

Hello

Hello

Hello

Hello

Hello