[v111] - Lidium

Page 2 of 8 FirstFirst 12345678 LastLast
Results 16 to 30 of 109
  1. #16
    Member SomeoneMs is offline
    MemberRank
    Aug 2016 Join Date
    65Posts

    Re: [v111] - Lidium

    Quote Originally Posted by JustATinCan View Post
    If you are stuck on that you need to change your "Lib" folder to "dist" that is what I did. @Echo off@title Lidium Server Consoleset CLASSPATH=.;dist\Lithium.jar;dist\mina-core.jar;dist\slf4j-api.jar;dist\slf4j-jdk14.jar;dist\mysql-connector-java-bin.jarjava -server -Dnet.sf.odinms.wzpath=wz/ server.Startpause

    I also changed my launch.bat up to make it more directed to my local dist folder. But the class paths are not working for me as you saw. So I am not sure what my issue is.
    ok now i get that:
    Lidium
    Loader 1...
    Loader 2...
    Loader 3...
    Exception in thread "main" java.lang.ExceptionInInitializerError
    at server.Start.run(Start.java:62)
    at server.Start.main(Start.java:121)
    Caused by: java.lang.NullPointerException: Cannot read the array length because "<local3>" is null
    at provider.MapleDataProvider.fillMapleDataEntitys(MapleDataProvider.java:39)
    at provider.MapleDataProvider.<init>(MapleDataProvider.java:35)
    at provider.MapleDataProviderFactory.getWZ(MapleDataProviderFactory.java:31)
    at provider.MapleDataProviderFactory.getDataProvider(MapleDataProviderFactory.java:37)
    at server.life.MapleLifeFactory.<clinit>(MapleLifeFactory.java:46)
    ... 2 more
    Press any key to continue . . .
    i think your wz not full?
    Last edited by SomeoneMs; 07-06-21 at 10:35 PM.

  2. #17
    Member JustATinCan is offline
    MemberRank
    May 2021 Join Date
    58Posts

    Re: [v111] - Lidium

    Make a wz folder in your C:\ drive root and extract the wz to that folder. He has pointers to point to that. He will make changes so make sure to keep a wz folder in your main folder as well when he updates.

  3. #18
    Member SomeoneMs is offline
    MemberRank
    Aug 2016 Join Date
    65Posts

    Re: [v111] - Lidium

    Quote Originally Posted by JustATinCan View Post
    Make a wz folder in your C:\ drive root and extract the wz to that folder. He has pointers to point to that. He will make changes so make sure to keep a wz folder in your main folder as well when he updates.
    right after the update:
    Lidium
    Loader 1...
    Loader 2...
    Loader 3...
    Loader 4...
    Loader 5...
    Loader 6...
    20947 items loaded.
    Loader 7...
    Loader 8...
    Loader 9...
    Exception in thread "main" java.lang.NoClassDefFoundError: org/apache/mina/common/IoHandlerAdapter
    at java.base/java.lang.ClassLoader.defineClass1(Native Method)
    at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1010)
    at java.base/java.security.SecureClassLoader.defineClass(SecureClassLoader.java:150)
    at java.base/jdk.internal.loader.BuiltinClassLoader.defineClass(BuiltinClassLoader.java:855)
    at java.base/jdk.internal.loader.BuiltinClassLoader.findClassOnClassPathOrNull(BuiltinClassLoader.java:753)
    at java.base/jdk.internal.loader.BuiltinClassLoader.loadClassOrNull(BuiltinClassLoader.java:676)
    at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:634)
    at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:182)
    at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:519)
    at server.Start.run(Start.java:85)
    at server.Start.main(Start.java:121)
    Caused by: java.lang.ClassNotFoundException: org.apache.mina.common.IoHandlerAdapter
    at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:636)
    at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:182)
    at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:519)
    ... 11 more
    Press any key to continue . . .

  4. #19
    Member JustATinCan is offline
    MemberRank
    May 2021 Join Date
    58Posts

    Re: [v111] - Lidium

    I just fixed that problem about 2 seconds ago. So the issue is that I had to re-name my .jars to what is in my .bat. Here:
    min-core.jar
    slf4j-api.jar
    slf4j-jdk14.jar
    you also need to recompile and fix your netbeans because it depends on those files when built. After that it fixed my issue and it loaded everything except this:
    LidiumLoader 1...
    Loader 2...
    Loader 3...
    Loader 4...
    Loader 5...
    Loader 6...
    20947 items loaded.
    Loader 7...
    Loader 8...
    Loader 9...
    [Loading Login]
    Listening on port 8484.
    [Login Initialized]
    [Loading Channel]Exception in thread "main" java.lang.NullPointerException: Cannot invoke "javax.script.ScriptEngine.eval(String)" because "engine" is null
    at scripting.AbstractScriptManager.getInvocable(AbstractScriptManager.java:67)
    at scripting.AbstractScriptManager.getInvocable(AbstractScriptManager.java:48) at scripting.EventScriptManager.<init>(EventScriptManager.java:60)
    at handling.channel.ChannelServer.run_startup_configurations(ChannelServer.java:118)
    at handling.channel.ChannelServer.startChannel_Main(ChannelServer.java:290) at server.Start.run(Start.java:91)
    at server.Start.main(Start.java:121)

    All I can read up online is that this is some issue with Java not loading script engines after JDK14? I might have to change my JDK to 14 and test not sure. (not a java guy and not familiar with it). Hope this helps anyone and if they have a solution to the above let me know I am out for the day. Well, to be exact the newer versions don't have a default engine anymore you have to define one I will have to look into implementing one and getting this running. I am interested on what the OP has to say.

    Thanks everyone for the commutive effort.

  5. #20
    Member SomeoneMs is offline
    MemberRank
    Aug 2016 Join Date
    65Posts

    Re: [v111] - Lidium

    Quote Originally Posted by JustATinCan View Post
    I just fixed that problem about 2 seconds ago. So the issue is that I had to re-name my .jars to what is in my .bat. Here:
    min-core.jar
    slf4j-api.jar
    slf4j-jdk14.jar
    you also need to recompile and fix your netbeans because it depends on those files when built. After that it fixed my issue and it loaded everything except this:
    LidiumLoader 1...
    Loader 2...
    Loader 3...
    Loader 4...
    Loader 5...
    Loader 6...
    20947 items loaded.
    Loader 7...
    Loader 8...
    Loader 9...
    [Loading Login]
    Listening on port 8484.
    [Login Initialized]
    [Loading Channel]Exception in thread "main" java.lang.NullPointerException: Cannot invoke "javax.script.ScriptEngine.eval(String)" because "engine" is null
    at scripting.AbstractScriptManager.getInvocable(AbstractScriptManager.java:67)
    at scripting.AbstractScriptManager.getInvocable(AbstractScriptManager.java:48) at scripting.EventScriptManager.<init>(EventScriptManager.java:60)
    at handling.channel.ChannelServer.run_startup_configurations(ChannelServer.java:118)
    at handling.channel.ChannelServer.startChannel_Main(ChannelServer.java:290) at server.Start.run(Start.java:91)
    at server.Start.main(Start.java:121)

    All I can read up online is that this is some issue with Java not loading script engines after JDK14? I might have to change my JDK to 14 and test not sure. (not a java guy and not familiar with it). Hope this helps anyone and if they have a solution to the above let me know I am out for the day.
    dammm we need change everything..rename and after recompile..maybe he need update the files..and make it easy

  6. #21
    Account Upgraded | Title Enabled! Halcyon is offline
    MemberRank
    Mar 2011 Join Date
    1,102Posts

    Re: [v111] - Lidium

    I miss v117.2. Cool that you're doing this for people.

  7. #22
    Member JustATinCan is offline
    MemberRank
    May 2021 Join Date
    58Posts

    Re: [v111] - Lidium

    He said he will make a fix and update. I miss 117.2 as well, I doubt anyone will feely make a working version on W10. But someone with the right knowledge could use this 111 and update it to 117.2. I am sure you can compare the working v111 with W10 to the non-working version of 117.2 and see why it is the way it is. I am still working on the engine part :/

    Edit: After reading graalvm has a script engine not sure why mine isn't working. I complied my lithium.jar in neatbeans with all the files in the graaljs folder. What am I missing?

    AbstractScriptManager.java reads as follows :

    try { path = "scripts/" + path;
    ScriptEngine engine = null;
    if (c != null) engine = c.getScriptEngine(path);
    if (npc) System.out.println(path);
    if (engine == null) { File scriptFile = new File(path);
    if (!scriptFile.exists()) return null;
    engine = sem.getEngineByName("graal.js");
    if (c != null) c.setScriptEngine(path, engine);
    fr = new FileReader(scriptFile);
    engine.eval("load('nashorn:mozilla_compat.js');" + System.lineSeparator());
    engine.eval(fr);
    } else if (c != null && npc) { c.removeClickedNPC();
    NPCScriptManager.getInstance().dispose(c);
    c.getSession().write(CWvsContext.enableActions());

    So, it points to graal.js but why is it null? not an expert mind you.

    https://golb.hplar.ch/2020/04/java-j...pt-engine.html

    Specifically it calls an error at engine.eval("load('nashorn:mozilla_compat.js');" + System.lineSeparator());
    I looked it up and to use this you need to enable
    System.setProperty("polyglot.js.nashorn-compat", "true");
    Will have to see what OP says since he's way better at java than me.
    Last edited by JustATinCan; 08-06-21 at 06:06 PM.

  8. #23
    Member 9sin is offline
    MemberRank
    Mar 2021 Join Date
    United StatesLocation
    52Posts

    Re: [v111] - Lidium

    https://discord.gg/deYbTkckBe
    Lidium Development Server

  9. #24
    Member JustATinCan is offline
    MemberRank
    May 2021 Join Date
    58Posts

    Re: [v111] - Lidium

    Still Having issues plz assist this noob haha

  10. #25
    Member 9sin is offline
    MemberRank
    Mar 2021 Join Date
    United StatesLocation
    52Posts

    Re: [v111] - Lidium

    Update mysql-connector-bin Ā· atnight348/Lidium@142d725 (github.com)

    The MySQL connector has been replaced with the newest version, which should have been the only one in there in the first place. I believe this was causing many people issues since they were probably importing both the old and new ones.

  11. #26
    Member JustATinCan is offline
    MemberRank
    May 2021 Join Date
    58Posts

    Re: [v111] - Lidium

    Can confirm that the changes made are working and I am playing on the server messing around with it. NOTE: The only flaw I saw was that someone changed in database properties password to be "root" make sure you match up your DB properties with your mysql password. (also in serverconstants.java)

  12. #27
    Account Upgraded | Title Enabled! ExtremeDevilz is offline
    MemberRank
    Apr 2008 Join Date
    647Posts

    Re: [v111] - Lidium

    Lol, guess this forum has become a joke.

  13. #28
    Member 9sin is offline
    MemberRank
    Mar 2021 Join Date
    United StatesLocation
    52Posts

    Re: [v111] - Lidium

    Quote Originally Posted by ExtremeDevilz View Post
    Lol, guess this forum has become a joke.
    when was it ever better lol

  14. #29
    Member SomeoneMs is offline
    MemberRank
    Aug 2016 Join Date
    65Posts

    Re: [v111] - Lidium

    Quote Originally Posted by 9sin View Post
    when was it ever better lol
    hey i see you close your server maybe you release your fix source?

  15. #30
    Member 9sin is offline
    MemberRank
    Mar 2021 Join Date
    United StatesLocation
    52Posts

    Re: [v111] - Lidium

    i will still accept pull requests



Page 2 of 8 FirstFirst 12345678 LastLast

Advertisement