Tiered Auto Fishing blocks. Works just like a vanilla automatic fish farm and pulls from vanilla fishing loot tables, but you dont have to stand there and make heavy objects hold down your mouse button.
Supports Forge or Fabric but not in the same jar.
Fabric versions still need the fabric-api. forge doesnt have any dependencies
Make sure that you are downloading the right jar for the mod loader you are using:
My file naming convention is fishtraps-{mod loader}-{minecraft version}-{fishtraps version}.jar (example: fishtraps-forge-1.14.3-0.0.1 is fishtraps for forge running on minecraft 1.14.3)
Fish Traps must be surrounded by water on all horizontal sides
Wooden Fish Trap: Reacts similar to a fishing pole with lure/luck of the sea 1
Iron Fish Trap: lure/luck of the sea 2
Diamond Fish Trap: lure/luck of the sea 3
Fish Bait: item that the traps use to lure and catch fish. Without it, fish traps are significantly slower (configurable)
Config Options:
Having an issue with the forge version. My game crashes from a ticking entity and it turned out to be the iron trap I had. It was fine until it got full and that's when the crashing started. Since emptying it, I haven't crashed. Here is the crash report https://pastebin.com/bdicUyJ3
In reply to Pandaling920:
cool. thanks for letting me know. uploaded 0.0.2 for forge. should be good now
Ya, I said I would soon. Ill probably start it today/this week.
In reply to ktboogey:
Yay!
Found Ender_Compass 2.1.1 which claims to work for Fabric and Forge with the same .jar file. Maybe it is easier to maintain if all is in one release.
But: Didn't test that thing yet. Was eager to tell you about me being happy :)
In reply to Konitor:
ya. I initially started with it in the same jar, but its just not worth it. Forge Tile Entity Handling is close to a total rewrite of Fabric Block Entities. For now im gonna keep them as separate builds and create a common code base(that probably wont have a lot of use cause.. differences)
In reply to ktboogey:
Then a hybrid mod is more like a proof of concept than a real life implementation?
For me it does not matter. When there's a mod I want to have I install the correct .jar for my MC version. This one I had on Fabric. Now I'm on Forge and I do really miss it. I'm happy to hear that it will be available for "Forgers", too.
Forge versoin?
In reply to FullMetalMaster1:
Same question from here, too: Is there a Forge version planned yet?
Nice, 1.14.3. Thanks so much!
OMG it only need the water on the horizontal sides..... I have just been wasting sooooo much space doing all 6 sides water sources lol I thought it was 6 so as to stop them from being able to be automated lol
in survival, how do I get the bait?
NM, I found the recipe.
I am still using 0.0.2 ver. of this mod and I have 0 issues with it. I completely understand the bait addition, it's just not something I want to deal with (I know you can disable it). With that being said is there really any reason I should update?
Thanks for a wonderful mod!
P.S.
I would like to see (if possible) the ability to disable or limit (change % of chance, perhaps) certain items from the loot table.
In reply to slickrip:
Thanks,
You don't have to update if you don't want to. i haven't encountered any breaking issues yet, so it should be fine.
The only things that would change the gameplay without the bait is - the config file wasnt added till 0.0.3, and i have removed the ability to add items to the trap (it works more like a furnace output slot now) cause i wasnt really intending on it to be a usable storage block.
So I have always planned on this to be using the vanilla fishing loot table. but since this is 1.14 you can always override the vanilla loot tables very simply with data packs. I might look into a custom loot table at some point, but for now a custom data pack will give you total control over the loot
Forge 1.14.2 was released today. I don't use fabric and I love fish farm mods and I'd totally download this mod. Can you mod this so it is run with forge?
In reply to aqrcn85:
Ya, I plan to build it for forge also soon
In reply to ktboogey:
Don't do it! Don't feed the forge trolls! Make them love fabric!
(But seriously, in my opinion you shouldn't. We need the community to coalesce behind one mod loader so we can stop waiting 1.5 years for updates and splitting the community between 5 different versions)
((To be completely fair though I've made a request or two for Forge mods to be ported I think, so I guess I'm kinda being hypocritical... But hey, Fabric is life!))
In reply to el0c:
So i'll start by saying I like fabric. The way its made is very clever and I will probably continue to code for it.
The problem is that fabric is designed for modders to use mixins. Using a mixin for something simple like altering a block field is great and makes it easy to quickly build and update a mod. But doing that makes it essentially a coremod and in modded minecraft where most modpacks are using hundreds of mods, Fabric probably wont be able to handle that without a lot of conflict issues because its up to each mod to alter the base class... the reality is that you need something like Forge to be able to maintain a standard API Hook layer so that you can run hundreds of mods that dont conflict with each other.
That being said.... this mod doesnt use mixins. it just extends a block with an inventory entity. so porting it between the two really wont be too difficult. Larger/more complex mods would have a much more difficult time porting
In reply to ktboogey:
I guess because I don't code mods for forge or fabric I can't really speak to those issues like you can.
My experience as an end user (i.e. installing mods like yours and using fabric in general for actual play) so far hasn't really given way to many of those compatibility issues between mods, and I'm using over 100 not including the base fabric stuff; but that may be due to the curation of mods and lack of duplicate/overriding/crossover functionality between most of them.
That's probably where my bias comes from, because it's working rather fabulously so far.
That said, more complex mods like ComputerCraft have recently broken and the dev has said with "limited time/motivation he doesn't want to consider it fabric compatible" for the forseeable future; so I can see your point about maintaining that layer so that modifications to core classes are handled by the loader and allow for a broad range of options with those hooks as their extended. If I follow what you're saying, it essentially puts most of the core modification work on the team who writes the loader; while mods are most independent classes that use the hooks to those core modifications.
(If I'm misunderstanding how Fabric or Forge or both works from a development standpoint; I apologize.)
But on that note; we then rely on it like we have for so long and get stuck dead in the water on progress because of some unforseen circumstance like MCP updates just stopping entirely.
This might have been overcome due to the rewrites they went through to start updating again, I'm not sure. I didn't keep track of forge.
But in any event, I personally feel like trading a loader that makes a lot of core modifications with a set of hooks pre-defined for one that leaves most of those core modifications up to the mod developer(s) provides a greater opportunity for clever mods and creative compatibility solutions between them as adoption of the loader rises.
Ultimately I guess it comes down to which you prefer as a developer. A set of tools or just the crafting bench. Most people (myself included for things like web dev) probably prefer the former; but I do love seeing the creations of those motivated to use the latter. Hell that's what gave us forge in the first place. I remember the days of Mod Loader releases on MC forums and how it was forever changed when forge came out. I guess I'm just hoping for the fabric renaissance :)
This looks really cool. Is this a Forge or Fabric mod?
In reply to BottenRastrd:
fabric. also needs the fabric-api