charles-t70

Lol, this whole forum is a joke. Slowpoke hangs out with the mod authors of the major mods that everyone wants to play, IRC means nothing. I ran a server with a guy that hung out on IRC the night RedPower 2 was released and was blessed by the presence of Eloraam on IRC and if you think that hanging out with LexManors and some Forge authors on IRC is something special, you're clueless. I'm done with these forums, there's nothing but ignorance, stupidity, lies, and a serious lack of help. Thank god I managed to figure the things out I that I needed in the little time spent here. Tekkit Lite is doomed to fail because the Technic team refuses to face certain realities. This is not to say this can't be changed, but the general attitude displayed by the little forum staff, as well as the way they continue to carry themselves will result in the end of their little journey soon. SMARTEN UP: Feed-The-Beast has you beat with mods, the developers behind them, and the community that has EXPLODED behind the whole movement. It would be in YOUR BEST INTERESTS TO: GO AND ASK FOR F&^%ING PERMISSIONS. STOP BEING IGNORANT CHILDREN AND GO AND BE CIVILIZED ADULTS. ASK for their intellectual properties, and you shall receive. Only you hold the key to your success, Technic Team, feel free to delete this as I assume you will. You, friend, are but a small sliver of filth that inhabits this forum and do absolutely NOTHING to help your Minecraft Community by being here. Change your attitude or get out, there's a big open world out there, go be a blight places other then where others seek help.

Last I heard there were talks of Mojang working on a Minecraft Pi edition, so maybe wait for the Tekkit Lite Pi edition (don't get your hopes up). Anyways, playing on this server would not be enjoyable, to say the least

MystCraft is extremely resource-intensive and Dense Ores ages or anything from the World Modifiers tab is extremely prone to crashing. The second a meteor crashes is usually an insta-crash for many systems, so without a crash-report or having previous experience with this issue, I'd have to say that your toaster will not be able to run a Dense Ores age. Have you tried upping the allocated RAM to your Technic Launcher?

This isn't the case at all, it looks like there are mistmatched IDs. Make sure your client has the exact same configs as the server at cpw.mods.fml.client.FMLClientHandler.disconnectIDMismatch(FMLClientHandler.java:529)

Good stuff, glad it worked out

Well like planetguy said: restrict agebooks. Unless you're running an absolute beast of a machine to host the server, it's quite the lag generator. The next update is supposed to get rid of a large amount of lag as well as completely change how you write ages, although that ultimately makes learning the age writing system at this point pretty much useless.

Yeah, it ends up being the same seed I'm not sure how to change the Nether seed

Well, if Railcraft's been removed from your server's mod folder, then there shouldn't be a coke oven in your house to cause any crashes. If you go into server's directory (If you run it from your PC, you should be able to locate this pretty quickly, but if you use an external host, you'd just need access to the server's FTP. Inside the main folder will be your /bin, config/, /mods and all the folders needed for your server. Download a copy of your entire config folder and then locate where Tekkit Lite was installed in your computer (if you didn't alter this, it'll be found in AppData/roaming/.techninclauncher/tekkitlite/config) and replace that folder with the files you downloaded from the server. You've now made sure you have the exact same configs! Can't say it'll resolve this issue for sure, but I don't know how many times simply doing that has solved issues that I didn't know had cropped up. -This line blames buildcraft: java.lang.NullPointerException at buildcraft.factory.render.RenderTank.a

That hello screen is FML loading. It's surprisingly quick with the Technic Launcher and seems as though it just pops up and disappears. Sometimes Minecraft takes a little to load and will hang on a white screen for some time after the hello window (Approx. 1 minute or more occassionally, depending on a few things) and will even go as far to say "Not Responding" should you attempt to move the window or interact with the white screen. Anyways, tough it out until it loads or your client specifically states "Minecraft has crashed!" at which point you should locate the crash-report that'll generate in your tekkitlite folder (AppData/roaming/.techniclauncher/tekkitlite/crash-reports), copy it to pastebin.com and link to that pastebin here. Fyi for next time, there's a bugs section found: http://forums.technicpack.net/forums/tekkit-lite-bugs.76/

Delete Dimension -1 in your world folder (Dimension 1 is The End). Pretty sure this changed in 1.4.6 or 1.4.7...not too sure.

It depends on what you intend to use Multiverse for, I guess. If you're using it to just create new worlds then MystCraft is the perfect mod for you and it's already installed (although extremely resource intensive), but if you intend to use it to bring worlds in, you need to follow a certain method in order to properly import a world as an age and have it looking anything like you remember it. Yeah, I can't get the import/load features to work either. It just returns "FAILED" and informs me it doesn't exist.

Glad it resolved, hopefully you don't run into it again.

Have you been following the updates to BukkitForge, though? It's come a long way. Current version build is 30

Does multiverse not? I thought it was one of the ones that worked for it. Take a look here for a list of plugins that should work: http://forums.technicpack.net/threads/bukkitforge-getting-bukkit-plugins-on-tekkit-lite.34804/page-8#post-297739 Here's a direct link to the version I'm using: http://ci.onarandombox.com/view/Multiverse/job/Multiverse-Core/lastSuccessfulBuild/artifact/target/Multiverse-Core-2.5.jar In the event you're not too fond of the direct link:http://forums.bukkit.org/threads/edit-misc-tp-fun-multiverse-2-3-world-management-bukkitdev.3707/ Look for Multiverse Core 2.5 (I've yet to try Multiverse Portals, but that'll allow you to transfer. Also, as a side note: last I saw they were advising that Multiverse with BukkitForge doesn't have the ability to create new worlds, you can only tp back and forth)

Are you able to reproduce this error in SSP or is it only happening when you enter a GUI in SMP?

Do these files also appear in your AppData/roaming/.techniclauncher/tekkitlite? May have been an issue when it was first generated, as I noticed this as well but upon further inspection I've noticed they've since generated normally in the tekkitlite folder.

If you're hosting from your computer, aside from the knowledge needed to set one up, you'd need to copy the world folder from your SSP world into the main folder of your server (with the /bin and /mods folders) and just make sure the server loads that as the default world, which is easily done by labeling it "world" when copying it to your server. It's essentially the exact same thing if you're using an external host, but you'd need to upload your SSP world to the server's FTP. If you're using default configs that came with Tekkit Lite, then there's no need to worry, but if you've made any changes I would suggest copying the configs from /roaming/.techniclauncher/tekkitlite/config into your server to make sure your server's using the same IDs used in your SSP world.

www.pastebin.com for future crash-report posting Have you tried reinstalling your tekkitlite instance (Back up any worlds and delete the tekkitlite folder in /roaming/.techniclauncher)? Edit: Make sure bcprov-jdk15on-147.jar is in your lib folder. If not, download it here: http://files.minecraftforge.net/fmllibs/

Whole thread pertaining to getting BukkitForge and plugins working on your Tekkit Lite server! Check it out: http://forums.technicpack.net/threads/bukkitforge-getting-bukkit-plugins-on-tekkit-lite.34804/ The latest build, 30, works perfectly as far as I can tell. It's just finding the right version of your favorite plugin that works with it

Is this SSP or SMP? If SSP and you're just generating a singleplayer world, I'd suggest trying to give it a bit of time to actually crash (may take a few minutes). If you stop it before it has time to generate a crash report, there's nothing we can use to help you figure out what's wrong, not to mention that worldgen in an SSP world would be based on the quality of your PC. It'll take longer for older systems to generate all of that worldgen needed. Look in /roaming/.techniclauncher/tekkitlite/crash-reports (if that folder got generated) and pastebin the last one here. -Ctrl+R then type %AppData% and hit enter to pull up the roaming folder (fyi )

Banning it would still allow the finished product to show in the output side, you just wouldn't be able to remove it from the table. Are you using RecipeRemover? (or, if you're using ForgeEssentials, does that have an option to remove recipes and if so, are there IDs in this area by default?)

I believe this has been cleared up. From what I understand, people have just redownloaded the server files for 0.5.2 and there must've been an update to the configs. Give that a shot (back up your current configs *just in case*)

Try going to http://files.minecraftforge.net/fmllibs/ and downloading the files you're missing (place them in your lib folder found in /roaming/.techniclauncher/tekkitlite/lib): argo-2.25.jar guava-12.0.1.jar asm-all-4.0.jar bcprov-jdk15on-147.jar From what I can tell it's just an issue connecting to where the fml-lib files are hosted. Anyways, hope that helps! If you don't find a lib folder in your tekkitlite directory, just create one and drop those files in to save FML the trouble of failing.

Have you tried making sure you've got the same configs as your server? Maybe something got displaced at some point...I've not run into this error before, but if you're the only one crashing and it's not causing the server to crash when this takes place, then that's as good of a place as any to start trying to resolve this.