WenjaHCF Release

[joeleoli]

MilkSkids is a meme

I was an owner of WenjaPvP until it shutdown. Source is on GitHub, and the Google Drive link contains the source and dependencies.
https://github.com/ijoeleoli/WenjaFactions
https://goo.gl/3pOuA6

Found the MySQL version:

This isn't a leak, it's a release

 

[Missionary]

No longer doing this, most people i tried to help are brain dead and dont know what a libary is or maven.

Most people that want your help don't know a lick of Java or they think that they are coding gods cause they changed a chatcolor.

 

[joeleoli]

You "previous projects" are just as shit, LMAO, just stop. Your project from only 9 days ago has more memory leaks than the public FactionsFly (https://github.com/ijoeleoli/ProPractice/). Keep trying to flex on me, you're not going to succeed, but I love it when you struggle

What are you trying to say by "the only work I've seen of his is GenBucket"? The difference between our skill level is quite clear. I don't need public plugins to demonstrate my skill and get myself known. However, if you really want to talk fame, I'm more known in the community you've been in for longer than I have while I've only been there for only a week or two.

Once you have genuine skill, you start to realize getting known or money is nothing and it doesn't mean shit to you. You start to do what you want without anyone being able to say shit to you.

How GenBucket shit? :3 I'd love an in-depth explanation of how it's shit and how any of your plugins compare to it. It's better than any project you have on your GitHub, and I have barely spent any time on it.

Oh boy he's back again. Not denying there is a memory leak, but go ahead and point out a memory leak in ProPractice.

As for your GenBucket, I'm just going to critique one class, "xyz.rinn.genbucket.data.Generating.java".

1. You're using a static initializer block to instantiate the "active" map, when it could've been done in the line where it was declared.

Example:

    private static Map<UUID, GeneratingBlock> active;

    static {
        Generating.active = new HashMap<>();
    }

could have been

    private static Map<UUID, GeneratingBlock> active = new HashMap<>();

2. You felt the need to declare the "active" map privately, when it's not needed. Doesn't really matter, but why private if it's not needed? You created more work for yourself.

3. Because of #2, you can't use the ALREADY PROVIDED methods of the HashMap outside of the Generating class. You improvised by "re-creating" the methods (you literally just took the data and used the HashMap's real methods). This is what I was talking about when I said you created more work for yourself. You could've just declared "active" publicly, and accessed the object from anywhere.

Looking at some of your other classes, you don't understand when to use final.

This doesn't really matter, but a lot of people prefer Google's Java Style. If you want to practice reusability, I would hope you would adapt to this. For example, after the end of each block or block-like structure, you use 2 line breaks, not 1... Just food for thought, you meme.

 

[Missionary]

Get the popcorn

 

[SkidSlayerOG]

No, you have to compile it yourself.

How I'm new to all this could you message me please

 

[SkidSlayerOG]

google.com
youtube.com

No for real I need steps from the person supplying it

 

[Missionary]

No for real I need steps from the person supplying it

Google.com
Type 'How to use maven' in the box and press the search button. That might help you.

 

[joeleoli]

Do you not know what static blocks do? Go read for fucking once instead of pulling shit out of your ass. Why would I make "active" equal to a new HashMap if I want to instantiate the class again?

What do you mean "why private if it's not needed"? You don't have a clue about memory management nor do you have a single clue what modifiers do?

I literally just explained it to you. There was no need for it to be private... you could've accessed the whole object from anywhere if it wasn't. When are you going to point out my memory leaks?

 

[Fle]

The fact that you two are arguing over a block game is fucking amazing.
Drop it.

 

[joeleoli]

The fact that you two are arguing over a block game is fucking amazing.
Drop it.

I did yesterday, lmao, he came back and embarrassed himself.

 

[Fle]

I did yesterday, lmao, he came back and embarrassed himself.

Just ignore him then.

 

[lucasPardita]

Are you still asking for the supplement?
DL: http://www.mediafire.com/file/9jzx7i87xabkugc/Factions.jar

 

[joeleoli]

https://github.com/ijoeleoli/ProPractice/blob/master/src/me/joeleoli/practice/player/PlayerData.java
https://github.com/ijoeleoli/ProPractice/blob/master/src/me/joeleoli/practice/party/Party.java
https://github.com/ijoeleoli/ProPra.../joeleoli/practice/game/duel/DuelRequest.java
https://github.com/ijoeleoli/ProPra...oli/practice/game/queue/data/QueuePlayer.java

Let's just store large objects everywhere! Why not, right?

How else do you expect to store information about a player you fucking mang? Should I make 73636 HashMaps in my PlayerManager class each with a different value type? I genuinely think you're retarded.

 

[joeleoli]

Maybe use something like a primary key, such as a UUID? Are you retarded? LOL. Sometimes you use UUIDs and sometimes you use Player, at least stay consistent in your programming style.

Oh so you'd rather have almost every action somebody does grab information from several hashmaps rather than have a designated class that withholds all that information?

You know, I'm not going to lie. When I started ProPractice, I probably did use Player in a couple HashMaps which is completely fucking retarded, but after I realized, I fixed them. There still might be some, but let me remind you that ProPractice is no longer being maintained by me, I commited that version on request, and that's not how I program. Feel free to point out where that happens, or even better, submit a pull request ::.

Regardless, you're still retarded and your code is shit.