If you'll excuse my totally chuunibyou nickname: Name: Sumeet `Hybrid` Padavala Social: Github: github.com/hybrideagle, IRC: hybrideagle From: Bangalore, India Skills / Tools: Java, Minecraft, ROS, Node.js, Python, Machine Learning/Deep Learning/AI, Hadoop, Kubernetes Found via: GSoC 2017 Interests: machine learning and AI(insert a thousand subtopics here), networking, procedural generation, aerial robotics, general automation, IoT, massively parallel systems(for the sheer awesomeness factor) Extra: Currently pursuing a CS undergraduate degree at PESU, Bangalore. Really likes Mr. Robot and Steins;Gate. Note: I'm quite new to the whole programming scene, so my interests are all over the place. For the same reason, I'm don't think I know which part of Terasology I could best contribute to. I've been looking through the code for a few days now, and from what I can see: The liquid system could use an overhaul. Maybe the CoreRegistry should be split up into different registries, with registration methods exposed as an API(one each for liquids, blocks, entities, etc)? The AI system desperately needs some love. Is there any sane way to restrict the types of objects allowed to go into the Context? It seems...wrong, for some reason, to be putting random objects in the Context(at least there's no weird reflection code though). I've also got a few GSoC ideas, should I put them in suggestions?