Dries007

Update 1.5: May or may not work with 79.17, build using 79.21 Added a heating screen Please report any incorrect items, if you find them. Vanilla TFC stuff should be ok, but I can't account for plugins!

I would still like to know what happened, just so I know if it might be preventable.

You have some damm fast reflexes...

Plug: You can do knapping recipes and much more if you install this.

I would make it more of a "Tools within reach" thing, where there is a list of tools in tool racks near (3 blocks?) the workbench. That would remove the limit of amount and type of tools you can require in recipes. Same with in-inventory crafting. If the tool is in your inventory, your good. (Perhaps a highlight of the tools that would be used in crafting would be good to avoid it using tools you don't want?) And if you want a more 'tiered' system, you could make the workbench have a 5x5 grid. I have so many complicated ideas.... I wish I had more time to work on them myself

This whole topic reminds me of Dwarf Fortress, that world gen is super intense. (but its limited in size)

Updated to 0.79.17 Make sure you download build nr > 19 if you use jenkins. The regular download link should be up to date.

I'm sorry I haven't replied at all. I've been busy with school and I didn't follow this topic so I didn't get updates via email when people posted. I'm going to try to get an update out today, if possible.

I have used ProfMobius' thing on HUGE mapswithout any issues, but I think its highly dependant on your servers CPU. Also, I think you are right about it not being worth updating the big plugins (essentials, WE, prizm, ....) because they are going to be updated to sponge eventually. But there are a lot of smaller things that will most likely never be updated. BUT: Sponge isn't done yet, and its implementation won't be stable or reliable for a while. (Also, because its forge, a lot of the things bukkit devs are used to will have changes, which makes updating that much slower.)

I started of doing small plugin like mods on the mc forums (homes, warps, crafting table command, enderchest command, virtual chest, .....). At some point AbrarSyed (the guy who makes ForgeGradle/GMCP nowadays) invitted me into the FE team because he had made a framework for permissions and data structures, but had no content. I then added a metric fuckton of (horribly coded) features without much documentation, because they were mostly taken from my smaller command mods, and I didn't want to write docs again. Just a quick sidenote: By this time I had 2 months of java experience, and was 15 yo. My only other programming experience was VB.net. Abrar didn't care because documentation was to be done when we were near a more stable state. And of course a new MC version arrives. By the time we were done porting stuff to the new version and started adding new features, MC updated. Repeat that a couple of times and you see why there was no documentation. At some point Luacs andMalkierian joined to help code,helinus started helping people in with questions on IRC. The 2 of us decided that, instead of updating the duct-tape-FE1 to the next MC version (idk which one anymore), we were gonna make an Abstraction layer. (Sponge avant la lettre) It was going to be awesome. Dynamically downloading/updating plugins, plugin reloading, ...... AKA way too much work for 2 teenagers in school. Abrar was fed up with MCP's .bat file system and started working on GMCP (the precursor to ForgeGradle), and stopped working on FE. Luacs wanted to go back to FE1, I did not, so I left. It didn't help that Forge kept promising blockPlace/blockRemove events and a central permissions system. By this time I had come to know Claycorp, who was in a little modding group with a programer and an artist (both of whom left because of Real Life time constraints). I did some work with them but they suffered of too-many-projects syndrome. In august we decided to start a new group and carry over some active projects, and it has been a fight for players ever since. We work together like this: He does all PR & docs, and I can focus on what I love. Coding. I do still have my own little projects (holoinventory, TFC-NEI) but almost everything is underDouble Door Development. Including the upcoming logger and maybe the ban thing (clay doesn't like them because he has 2 mcbans bans from way back when). TLDR: I'm sorry FE sucks. wow. many words, such post.

@Bunsan Just so you know: I was part of FE then, and most of the lack of documentation might have been my fault

@Bunsan that api looks useful, that is most of the work done right there A mod using fishbans.comwould not be able to report bans to any of the subsystems, but it would be very simple and quick. You could just set a policy (0 tolerance, only count mcbans, ...) in the config and just refuse logins if you aren't on an exemption list. Or just send a warning to an admin. How does that sound?

Besides D3Log (which is an upcoming Forge logging mod a la Prism), I would like to help by making a lot of the simple things, but I don't really know where to start. I would love some priorities, soI made thisto help. DM me an email address and I will let you edit this.

So someone just made an awesome PR, the barrel recipes now look like this:

Little update on my side project: Thanks to prism being open source, I'm now down to implementing all of the events and the rollback functionality. The database design and logging engine are pretty much a 1 to 1 port of prism (with some adjustments for forge).

What do you think of the op now? I think that should suffice.

I will add a little message to the op about the data collection. As far as I know, i'm one of the only developers who use mcstats, most devs seem tot use a homebrew system (if they use one at all) but I prefere something that is open en known. (At least known in the bukkit community)

I fixed the OP, you think it will be better now?

The problem is that I know I will forget. I'm going to make a redirect I think.

I did add a nice big banner to the jenkins page, but then I had to do a rollback. It is back now.

You are damm quick Kitty...

I don't know how prizm works, and I would prefer getting a small TLDR instead of having to go through the entire plugin

@Djakuta can you compile an absolute must have list for a public server? I'm talking about a brief description, not just a name of a plugin. I get from your post that you want: - Logging of all block changes - MCBans support (?) I just came across this topic, and wanted to say that we have been working (on and off) on a logging thing for Forge.

Since this mod is open source, you can check to see that I'm telling the truth: I added PluginMetrics (the thing all bukkit plugins use), its source is also open. -> Github The statistics outputted by this plugin are also openly visible. -> (Site is a bit slow atm) Here There are a few issues with the metrics system, specifically thePluginMetrics.cfg file. That includes the random unique identifier used to id the same user, so if people include that in there modpacks, it screws up all of the stats. As far as I'm aware, there is nothing illegal (or wrong/dishonest) with sending anonymous statistics. Also, why would you opt out? It gives me a false sense of how many people are using the mod, and it discourages me from developing on it, as it seems like noone is using it.

I'm migrating from a vps to a dedigated server and Jenkins needed to be down for it to transfer over 2,GB of data. It should be back up in a day or so. Sorry once again. -.-