ask where install on ubuntu (because by default it's on ~/) about hafen-client

[EnderWiggin]

it should downloads into the current working dir not sure how to control that on Ubuntu or other linux distros.

[Fr-Dae]

~/haven/ for ./
could you show me what files manage download, i can maybe check

[EnderWiggin]

https://github.com/EnderWiggin/haven-launcher/blob/62ce0f71a076d9831d5a98b24e2f95c8d74aa520/src/haven/launcher/Utils.java#L216-L224C6

[Fr-Dae]

/src/haven/launcher/Utils

/src/haven/PUtils.java
/src/haven/Utils.java
/src/haven/RUtils.java

• first problem,
  I can't find the same folder structure as you.

• Second problem, why do you have several repos for the same project? Can't you merge the repos and make it easier to read and modify the project?

• The repos that you don't use or no longer use, can you please put them in "archive" which will prevent visitors from getting lost in your multiple repositories.

It is typically for this kind of discussion that I would like to be able to discuss with you via mail, or discord, because conversation in github issues is absolutely not practical.

[Fr-Dae]

could enable the possibility to make Issue and PR on please
https://github.com/EnderWiggin/haven-launcher/

[Fr-Dae]

https://www.oracle.com/java/technologies/javase/codeconventions-contents.html

following Java naming conventions is crucial for writing clean and maintainable code. Here are some best practices and details regarding naming conventions:

• Class Names (PascalCase): Start the class name with an uppercase letter, and if the class name consists of several words, each inner word should also start with an uppercase letter.
  For example:

class MyClass {
    // Class body
}

• Variable and Method Names (camelCase):
  Begin variable names with a lowercase letter and capitalize the first letter of each subsequent concatenated word. Methods should follow the same convention.
  For instance:

int myVariable;

void myMethod() {
    // Method body
}

• Constants (UPPERCASE_WITH_UNDERSCORES): Constants should be in uppercase letters, and if the name comprises multiple words, separate them with underscores.
  For example:

static final int MAX_SIZE = 100;

• Packages (lowercase):
  Package names should be in lowercase letters to avoid conflicts with class names.
  For example:

package com.example.mypackage;

• Meaningful and Descriptive Names:
  Use meaningful and self-explanatory names that convey the purpose or functionality of the variable, method, or class.
  Avoid using single-character names or cryptic abbreviations.

• Avoid Underscores for Class Names:
  While underscores are allowed in method names and variables, they are not recommended for class names.
  Class names should use PascalCase without underscores.

• Be Consistent: Maintain consistency throughout the codebase.
  If you're working on an existing project, follow the naming conventions already established.

• Follow Standard Naming Conventions:
  Adhere to standard Java naming conventions documented by Oracle, Google, Apache, and other reputable sources to ensure your code is easily readable and understandable by other developers.

• Use Javadoc for Documentation:
  Provide clear and concise documentation for classes, methods, and variables using Javadoc comments to explain their purpose and functionality.

By following these naming conventions and best practices, your Java code will be more consistent, readable, and comprehensible for yourself and other developers who might work on the same codebase.

[Fr-Dae]

up ?