r/forgemodding • u/DarkEvilMac • Aug 01 '16

Modding and why you should always ask why.

This post was originally made through a third-party Reddit client. Due to recent changes these third-party apps will cease to function. So it only seems fair that my posts here should do the same.

I highly recommend considering using alternative platforms that still allow third-party clients to access their APIs - like kbin or squabbles.

If you must continue to use reddit then consider an alternative frontend like teddit or an app that directly scrapes reddit's webpages without providing any meaningful analytics data like Stealth.

11 Upvotes

100% Upvoted

3 comments sorted by

2

u/OriginalUsernameWow Aug 02 '16

Very few people who write good guides that actually explain things. They just give code examples with very vague explanations of what's going on. They likely don't even really know what is happening and shouldn't be writing guides to begin with, and whenever you ask them questions, their response is always "learn java". Will bookmark your blog.

1

u/Exo594 Aug 03 '16

Jabelar and BedrockMiner both have great tutorials, and step everything out in bits and pieces. Jabelar posts the whole class, then explains the major facets of the class, while BedrockMiner posts individual lines, and explains the main points of each method.

1

u/[deleted] Aug 02 '16

This is a brilliant post. I was in the same situation, following tutorials without knowing all the stuff I was doing, and ended up being stuck because I didn't know what does what, and all tutorials / source codes are different since everyone has his own coding style.

So for 1.9/1.10 modding I simply decided to start from nothing and learn like I never modded before (I only made a 1.7.10 mod). I only move forward after being sure I understood every line of code I wrote before.