Leaderboard

There are different aspects to modding. I started to create custom content with Jeremy McGrath's Supercross 2000 for the PS1, making custom tracks. I loved it so much, I'd spend hours making new combinations. Things get pretty foggy, but I'm pretty sure my first game I actually modded was Halo: Custom Edition with the SDK, the Halo Editing Kit. It came with a proper set of tutorials, and on the web there was plenty of documentation as well. This was not enough, though, and I went out of my way to buy games that either had SDKs or community-developed tools to mod games, including (but not limited to) Freespace 2, F.E.A.R., Source-based Games, LegoRR and Flight Simulator X. The more I modded, the more I learnt about computers in general, and the more I was inspired to try other programs and learn to program, model, animate, create sounds, movies and level design. Eventually I downloaded special programs like Adventure Game Studio, Unity, UDK, CryEngine, Game Maker and so much more. They're very good engines with great support and help documents, designed to allow anybody to make a game. The key is to find tutorials on the web, written in a style suited to you, and following them to the letter at first, and then mixing them up and trying out new things, until you become confident with the process and you can do it your own way. Sometimes authors will take odd steps or a long path for different reasons, so I like to pursue finding out why the author performed all the steps they did, and what they actually do towards the finished product. Of course, one way is to self-teach, as I (mostly) did for animating (help from Cirevam and some web tutorial to enhance my knowledge and help me do somethings I would have never thought of, of course). Play around with a program for an hour and you might learn some interesting new things. Of course, it can never beat help from a professional, but it's a good way to become acquainted with the basics. One other thing, you can learn to program at Code Academy (google search them). They're brilliant online, free, tutorials that teach you exactly what you need to know and give you practical experience, and tell you every mistake you make so you can improve yourself. Also, I learnt C through the C All-In-One Desk Reference for Dummies, with author Dan Gorkin, whose amazing at writing his self-help books. Once you do learn, it's about first considering the problem, and looking at all the steps you would need to perform to create the solution. Break it down to some very simple steps, and you'll be able to code a program in no time.

... wat. First, as mumboking said, that's an incredibly awkward and inefficient texture size. Second, even 1024x1024 might be a bit much IMO (for things like grass and dirt and the like), 512 x 512 should be fine for most stuff like that. No need to go to absurd texture sizes when the camera probably wouldn't ever get close enough to the ground to warrant it. Just try it out and see, only go for 1024x1024 if 512x512 isn't satisfying.

pot calling the kettle black

We have been impressed and encouraged with the dedication of our Rock Raiders fans, and after years of requests we are looking at creating a new Rock Raiders. We are considering combining a mine craft style world, so you can build and dig in more ways, please tell us what you think?

Where did I learn everything I know? From tinkering with computers and software for the past, what is it now? 4 years? Basically, modding requires reverse engineering the data files to change something, then you can write a program to automate this (my current preference is Python because it has some nice binary file capabilities that I can write software quickly with). So, to reverse engineer something, it helps to know what you are looking at. In the case of LEGO.JAM, it was pretty clear it was a file archive of some kind that contained all the data for the game. Thankfully, there were already partial file format specification which enabled me to make an extractor (this was my first time reverse-engineering). Anyway, a simple file archive generally has a list of files and their offsets and sizes so that they can be found within the binary data. Image files on the other had would have some kind of pixel map, and 3D model formats have vertex coordinates and other information to form faces. Most of the time, it's just guess-work, looking at the binary data in a hex editor, and trying to make sense of it, testing by modifying bytes and see what changes.

I kind of got epicness when, at the end of Portal 2 Also at the end of Lego Racers, when you see Rocket Racer for the first time. :lol:

Lair? Sane? Pffffffffffffff Welcome to RRU. Don't wear any pants. We need to overthrow extreme. @Le717 Chill. Some bronies you wouldn't be able to tell that they're bronies.

Oh come on, even 1024x1024 would be fine. 3008 isn't even a power of two. About the quality difference, it depends... Try it and find out. Some pictures will look good, others not so much.

This is a forum about Lego stuff particularly games(which Galidor has BTW) and Lego made it a Lego theme so why should it? Because saying Galidor is LEGO is like saying personal pizzas from Subway are Italian cooking. Maybe, but I can still make a topic about it. Or can I? Of course you can, just don't expect too many people to leave replies on how much they love the theme. It's got a bit of a reputation in the LEGO community for being one of LEGO's greatest failures... :P

This is a forum about Lego stuff particularly games(which Galidor has BTW) and Lego made it a Lego theme so why should it? Because saying Galidor is LEGO is like saying personal pizzas from Subway are Italian cooking. :P