JademusSreg

Here's a simple, concise, and legible approach to setting up your Voltz server (1.0.5 for Minecraft 1.4.6). Download the Voltz_Server_v1.0.5.zip, or a comparable version for your Minecraft version. Unpack the Voltz_Server_v1.0.5.zip file to the desired directory. Execute the Voltz.jar.

Provide crash logs.

Mine straight down until I fall into lava and die.

Also, press O, the hotkey for toggling NEI.

My apologies; I used the Tekkit page on the main site as a reference, and it incompletely reads "3.1".

Set your Tekkit version to 3.1 and force update in the launcher options.

Wiktionary says morre is the subjunctive singular of morren, which apparently means "to groan". All rather moot, though, since Mojang is a Swedish company.

That's consistent with information about the Redstone Update. EDIT: According to GoogleTranslate, Dutch "morre" means "having fun".

The internet is magic.

Not.

Less interested in assholery, more interested in malfeasance. If Sylais had elaborated on the FTB misconduct barely mentioned in the third paragraph and cut all the irrelevant shenanigans (which is to say everything else), it would have made a better impression. To put it differently, making tactless public statements, like those that take cheap shots [unavoidable pun] against Slowpoke or whoever on FTB, impairs your credibility. Not that you should self-censor; instead, be clear about your purpose. You can communicate cogently and make a point, or you can air your grievances, but don't do both in the same conversation.

It would appear the FTB folks are in the process of addressing the (hilarious) issue.

Lamenting over a problem isn't an efficient use of time; better to apply yourself to a solution, or otherwise determine the problem isn't worth solving. Can't use plugins in a post-Bukkit Tekkit? Make some server-side Forge mods. Can't program the mods alone? Collaborate with others, put it on Github, invite everyone to the party. Can't be bothered to contribute to a solution? Wait it out on Tekkit 3.1.2 until more server mods become available.

Good news regarding the maybe-possibly-soon-updated Tekkit mods. No concern about decompiling or deobfuscating, though, given the Tekkit server pack isn't so tightly bundled, so to speak; mods can be implemented easily via the /mods/ directory. Changing Forge and fixing the mods and such, on the other hand, would certainly be challenging without a source to fork, hah. Seems the only option for writing testable Tekkit-specific code is to use Forge 3.3.8.164, short of a Tekkit development build or word from the powers that be. Updating the code isn't so much of a hassle it merits waiting.

Sounds dreadful, but it appears I'll need to code for Forge 3.3.8.164; much as I would prefer to use 4+, I wouldn't be able to test Tekkit-specific features (EMC, EU, MJ configuration and such), unless I manage to wedge a 4+ version of Forge into my Tekkit server.

My apologies for the misunderstanding; I'm not asking how to handle the impending lack of Bukkit plugins, but rather am asking which Forge build I should use to program server-side mods. To clarify, I am not worrying about plugins; if I need a feature, I'll code it. That said, it would be helpful if Tekkit's curators or anyone comparably well-informed could elucidate which Forge build plugin-substitute developers should be using. The differences between pre- and post-4.x builds are significant, with regards to the more event-based API and client-server merge, and it would be a dreadful waste to code everything in 3.3.8.164 only to have Tekkit update to 4.x (or even 6.x) shortly after. That is to ask, how long should those developing plugin-substitute mods for Tekkit expect it to continue using Forge 3.x builds?

Given recent news of Forgebukkit's end, I'm curious which Forge build I should use in programming replacements for the Bukkit plugins my server currently employs (and other features in the pipeline). The Tekkit server setup I'm in the process of prototyping will take a number of months to bring to alpha, which is to say I'm taking the time needed to code and test essential features before launch. However, I'd like to know which version of the Forge API one might expect to be implemented when Tekkit gets around to dumping Bukkit. Is it a safe investment of time to code server-side mods under Forge 3.3.8.164, or should one focus on Forge 4+ with the expectation Tekkit will make the transition "soonish"? Or should the worst be expected, Tekkit stuck on increasingly outdated dependencies, its userbase unwilling to relinquish Bukkit plugins?