Jump to content

help pls quick


ejer

Recommended Posts

1 minute ago, Differentiation said:

1. Rename your packages.

2. If you do NOT know Java, I suggest you learn some before starting to mod.

1. why

2. i dont know java and i just started with a tutorial and i messed something up but then i repaired it and now there is this :/

pls help not tell me how to live my life

Link to comment
Share on other sites

3 minutes ago, ejer said:

why

1. You clearly don't know the right way to handle packages

3 minutes ago, ejer said:

2. i dont know java and i just started with a tutorial and i messed something up but then i repaired it and now there is this :/

pls help not tell me how to live my life

2. Please don't. Tutorials have an end, then all you do is mess up your mod further on. Your mod will get harder and more intense as you progress and if you do not know Java, then you will get lost.

I would recommend you have some basic knowledge of Java before you begin with your project.

Just a tip.

Edited by Differentiation
Link to comment
Share on other sites

Just now, Differentiation said:

1. You clearly don't know the right way to handle packages

2. Please don't. Tutorials have an end, then all you do is mess up your mod further on.

I would recommend you have some basic knowledge of Java before you begin with your project.

Just a tip.

ok but just tell me how to fix that please

and i just wanted to do whats in the tutorial so i just want to finish it and thats it

Link to comment
Share on other sites

12 minutes ago, ejer said:

ok but just tell me how to fix that please

 

Rename the first package (com) to com.ejer.first

and then inside that, make packages for common and client side code.*

Then sort your packages in these two packages accordingly.

OMIT example.examplemod.

 

*If you do NOT know the differences between client-side® and server-side® code, please disregard this step.

12 minutes ago, ejer said:

and i just wanted to do whats in the tutorial so i just want to finish it and thats it

That'll only teach you to make one item, and one block.

Yeahhhh... not a very good idea :/

Edited by Differentiation
Link to comment
Share on other sites

24 minutes ago, Differentiation said:

Rename the first package (com) to com.ejer.first

and then inside that, make packages for common and client side.

Then sort your packages in these two accordingly.

OMIT example.examplemod.

That'll only teach you to make one item, and one block.

Yeahhhh... not a very good idea :/

sooooo this happened

help2.PNG

i renamed ejer.first to ejer.first2 and then com to com.ejer.first

Edited by ejer
Link to comment
Share on other sites

12 minutes ago, ejer said:

sooooo this happened

help2.PNG

i renamed ejer.first to ejer.first2 and then com to com.ejer.first

No.

You're doing everything wrong.

Whenever you create a new package, you have to add a . and then the package name.

Please follow your tutorial.

I cannot explain much further because this cannot get any simpler to understand...

Link to comment
Share on other sites

On 29.10.2017 at 8:11 PM, Differentiation said:

It's supposed to be structured this way.

 


►MDKExample
	►src/main/java
		►com.ejer.first
			►proxy
			►init

Something along these lines.

I DID IT LIKE THIS AND I WASNT DOING ANYTHING WRONG I KNOW WHAT YOU MENT BUT IT JUST SPLITTED IT UP      R E A D   W H A T   I   S A I D

 

On 30.10.2017 at 6:59 AM, diesieben07 said:

Ok, guys, seriously?

 

There is nothing wrong with these screenshots. Why do think there is? They represent the desired package structure perfectly.

However:

  • You should not keep the examplemod.
  • I doubt you own ejer.com, so don't use that package name.

im concerned that that it would mess up something and i just wanted to keep it com.ejer.first and i own a domian but not exactly com so im gonna change that soon

Link to comment
Share on other sites

 

On 29.10.2017 at 8:10 PM, Differentiation said:

No.

You're doing everything wrong.

Whenever you create a new package, you have to add a . and then the package name.

Please follow your tutorial.

I cannot explain much further because this cannot get any simpler to understand...

 yes i am doing every thing right i renamed it bc there was one there already and i couldnt rename it and then it split up i didnt do that manually i was following my tutorial i know how to name packages "Whenever you create a new package, you have to add a . and then the package name." 

Link to comment
Share on other sites

2 hours ago, ejer said:

okay you know what?

here just have my files and send me back the repaired ones:

https://ufile.io/kt4fl

 

- The odds of someone downloading a random file from the internet is pretty slim.

- What will you do when the next thing doesn't work? You'll run out of people willing to fix stuff for you.

 

You need to learn Java, and how to work your programming environment, BEFORE you try to learn to mod. It's not people trying to "tell you how to live your life", it's the rules of this forum, and just plain good advice. Learning Java through modding would be kind of like learning how to swap out an engine in your car with 0 automotive knowledge. . .and still needing to drive it to get to work.

  • Like 1
Link to comment
Share on other sites

Guys, the original question is really simple -- it isn't actually a problem at all. In Eclipse there are two ways of displaying the packages. There is a little down arrow in the top of the package pane that brings up a menu and in that there is Package Presentation. There are two options "Flat" and "Hierarchical". If you choose flat it will show the full package names "com.ejer.first" and if you choose hierarchical it will only show the full name if there are no other sibling packages. For example, in hierarchical if you start by creating a package called "com.ejer.first" then it will show it that way, but as soon as you create another package called "com.examplemod" it will then show them both in a directory tree "com > ejer.first" and "com > examplemod".

 

In other words, your package is still properly com.ejer.first, it just displays as a folder explorer.

 

So basically there was nothing wrong in the first post. That is the way hierarchical view looks.

Edited by jabelar
  • Like 2

Check out my tutorials here: http://jabelarminecraft.blogspot.com/

Link to comment
Share on other sites

5 hours ago, jabelar said:

Guys, the original question is really simple -- it isn't actually a problem at all. In Eclipse there are two ways of displaying the packages. There is a little down arrow in the top of the package pane that brings up a menu and in that there is Package Presentation. There are two options "Flat" and "Hierarchical". If you choose flat it will show the full package names "com.ejer.first" and if you choose hierarchical it will only show the full name if there are no other sibling packages. For example, in hierarchical if you start by creating a package called "com.ejer.first" then it will show it that way, but as soon as you create another package called "com.examplemod" it will then show them both in a directory tree "com > ejer.first" and "com > examplemod".

 

In other words, your package is still properly com.ejer.first, it just displays as a folder explorer.

 

So basically there was nothing wrong in the first post. That is the way hierarchical view looks.

Obviously he's using hierarchical but he is getting errors so that's his problem. 

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.



×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.