thomasfn
-
Posts
47 -
Joined
-
Last visited
Posts posted by thomasfn
-
-
Version 1 - 4 are for very old versions of Tekkit. I've just removed them from the OP to prevent confusion.
The version numbers now correspond to the Tekkit version they target. For instance, 311a targets Tekkit 3.1.1. The letter ("a" in this case) indicates the version of the patch. The latest version of the patch is 311a. I did order the download list such that the top one is always the newest.
On this note, has anyone tested the patch to see if it works with 3.1.2 or 3.1.3?
-
Not too sure about the other issues as I've never really run a big server myself but to fix some of the EE tools bypassing worldguard you can use this. You'll want to disable any of the EE tools not listed as patched in that thread.
-
I'm looking at the blockplaceevent API right now, and wouldn't it be possible to: lie to bukkit, say they had a lava block in their hand, and use the orb's hit detection to determine the block it was placed against?
I'm certainly no expert at bukkit's API, but it seems to be asking the plugin all these things, instead of filling them in for you. please correct me if this is incorrect though, I really want to learn how bukkit handles its events (ive been modding vanilla MC, but i really want to move onto bukkit plugins) and if it would be possible to fix these tools to not be such excellent griefing tools. They may be only able to place tnt 4 blocks into protected regions, but it still blows up (and i don't want to have to disable tnt explosions in regions).
also: it's probably just factions, seeing as that's the plugin creating the regions, I'll check into it. it's a nice accidental feature though
Thing is, the player can look up into the air and place water all in the sky - no blocks are even being right clicked against.
-
Pretty sure I did patch the lens, and as for the amulets, they create blocks (which is hard/impossible to patch because the BlockPlaceEvent expects the player to be holding a stack of items and to have right clicked against a block face).
Not sure about the tools discharging when you leave a protected area, never seen that behaviour before. Might be a funky plugin.
-
I was digging around the code because i really wanted to fix the last few items up, and wanted to check how you did it, and I must say, Some of these tools took a bit of modification to work, so thanks for that (why on earth would you make a tool that registers itself as the world instead of the item's owner?!). but also, a bit of a complaint: Why did you change the style of the files? the originals took up a lot more lines, yes. but it made for clearer organization, and made sure certain functions were for sure inside others. Also: when tearing through the files, determining exactly what you had to change, it makes the differences show up like crazy, even though most of them are style changes. What I'm trying to say is: don't fix what isn't broken. The tools' block breaking was broken, the style was not.
In the end: thanks for the patch, it's really helpful, could you possibly finish up the last 4 items? that would be really helpful (if you wont: how would i go about it, would i have to break the blocks then place them all again, or is there some easy way of block replacement? (i assume there has to be, for furnaces and RS Ore))
update: taking a look into how the amulets work: is it even possible to link them back to a player? it seems to make the essence ball, then do nothing else, and the essence ball is made by the world (i think) so if that one is possible, it's a lot harder than the other tools
Just so you know, the compile/decompile process does not preserve the "style" - what you see is completely reproduced from Java's virtual machine code. I decompiled the code, added the fix, and recompiled - nothing else was changed.
Also, I believe furnaces and RS ore use metadata and not seperate block IDs (though I could be wrong).
-
You could also try using a sponge. Not sure how much range it has though.
-
It works on 3.1.2.
Thanks, updated the OP.
I just wanted to say thank you for making this modification and providing it to us all here. It is invaluable to my own server and I don't think I would even run a Tekkit server if it wasn't for this modification that is how important it has been to me and my server.Thanks again.
You're welcome, glad the patch is helping you!
-
Yes, try a different plugin, this is the first I've heard of that kind of behaviour. Also I'm sure you probably did, but check your server console/log.txt for any errors (or is that what you mean by problems with your sqldb?)
-
If he releases those fixes publicly, with his permission I could include that in this patch.
Also, as a general rule, if EE doesn't get updated, the patch should still work fine.
-
This requires Java 1.7 I believe. Honestly I don't really understand java versions but if you don't have 1.7 it errors at you so yea.
Also Hellocreeper, are you using the latest version of the patch (311a) and on a Tekkit 3.1.1 server?
-
Identified and fixed the red morning star problem, and updated the patch to link against Tekkit 3.1.1. Try this patch: http://www.sendspace.com/file/ffgdky
-
I have done the patch against a 3.1.1 live server.
Its 'working' but throwing a ton of errors.
I spoke with a few @ #mcportcentral they said it looked like it was the red morning star.
That's weird, the morning star uses the exact same code as every other tool to fire block break events off. Does it happen with any other tool, or just the morning star?
-
The Yogscast publish Tekkit videos to their channel(s), and they're definetly a youtube partner. You have nothing to worry about.
-
Whenever I'm in the mood to do it. It also depends on if any of the EE tools changed since the last update - if the code for the tools hasn't changed, it should be just a case of linking against the newer Tekkit jars.
Can someone try applying the patch to the 3.1.1 server and see what happens? Does it work as expected? If it doesn't, are there any server errors?
-
Perhaps try disabling your texture pack or increasing the amount of RAM allocated to Tekkit.
-
According to the front page announcment they've tweaked the server as it was under alot of stress due to sheer numbers, so far this seems to have solved the issues for me.
I'm also 95% sure this thread is in the wrong section.
-
Played the dev map a bit, it's hard - we basically have to farm zombie pigmen and zombies to get enough gold nuggets and iron bars to progress, and them zombie pigmen hit hard (and they spawn around the nether portal in the dozens).
-
I seem to be having some issues too. Sometimes it will say "Can't connect to minecraft.net" and it will also say in the news box "Oh no our Tumblr feed seems to be down!", then I'll restart the launcher and it will work fine. Also the initial "Checking Launcher Version.." box sometimes just hangs at 0%, or crashes completely with a "TechnicPackUpdate.exe has stopped responding" windows error.
-
@thomasfn
THANK YOU
so i noticed you have investigated into the rings and amulets, they work differently then the red and dark tools?
Here goes.
Patching tools which simply destroy blocks is easy. I create a BlockBreak event, which only cares about the block in question and the player - then I send it to bukkit.
Patching tools which place or replace blocks is hard. The BlockPlaced and BlockCanBuild event expects there to be a player who's holding an item, as well as what block they're aiming at and what side of the block they're aiming at. This is completely irrelavant for tools such as the evertide amulet, which can arbitrarily spawn water in the air. Same goes for philosophers stone - there's no event for BlockChanged or something, I'd have to pretend the player broke the sand and replaced it with grass or something. It'd get messy and break and wouldn't work right. So that's why.
It's something I could maybe do with alot of work and fiddling, but honestly why should I? It should be the task of whoever ported the mods to bukkit to do this, not me. Hence, I'm only going to patch destruction tools because they're easy (and the most... destructive, in the hands of a griefer).
-
Updated the patch formally to Tekkit 3.0.4. Also extended the patch to 5 new tools/items:
- Destruction Catalyst
- Hyperkinetic Lens
- Catalytic Lens
- Nova Catalyst
- Nova Cataclysm
Download can be found in the OP.
- Destruction Catalyst
-
The morning star and indeed all patched tools should be working with both protection plugins and anti-griefing plugins. The AoE functions of the tools reports a block break event for each block affected by the AoE, so your antigrief plugin should see the function just as if the player dug out all those blocks normally.
-
I've been "delaying" answering that question because I'm not sure about the answer yet. I could, maybe, it depends how much free time I get and it depends what the code looks like.
-
Try this class file for the axe: http://www.sendspace.com/file/qf8gbl
-
I took a look at the phil stone. The problem is, Bukkit has events for breaking blocks and placing blocks, but no events for changing blocks - which is what the phil stone does. I thought about throwing a break block event then a place block event straight after, but the place block event has information like which side of the block the player right clicked on and such and it's just going to cause problems. I'm not too well versed with the Bukkit API so maybe I'm missing something.
I should be able to do other tools that destroy things though, such as the destruction catalyst.
Has anyone tested the patch on the new 3.0.4 update? Does it work?
Patch for EE mining tools - no more griefing with them!
in Tekkit Classic Discussion
Posted
You failed to install the patch correctly, by the looks of it. You need to merge my patch with the existing EE files, not override the zip file completely. Revert to a backup and try again, following the instructions letter for letter.