Jump to content
Eternal Lands Official Forums

bluap

Moderators
  • Content count

    2985
  • Joined

  • Last visited

Everything posted by bluap

  1. Can't log in - The rules.xml file was not found

    I committed the needed changes to git. The client should compile and work with anything other than v2.11.
  2. Can't log in - The rules.xml file was not found

    Which distro are you using? On Arch for example, I have installed the old version and will hold the package until the updated version arrives. If you build your own package, most packages will support installing into the /usr/local tree which would be picked up by the build and at runtime, hopefully. If not you may have to remove the old package too.
  3. Can't log in - The rules.xml file was not found

    Thanks for finding the problem with my additional checks, that could have lay hidden for ages. Glade you fixed your audio, we'll need to keep a look out for that.
  4. Can't log in - The rules.xml file was not found

    Wow, that's an unintended consequence of adding the return value check for the read_actor_defs() call! I've had a quick look at what you have found and I think you found a long standing bug. If the statement: if (!have_sound_config) return 0; returns zero, the defs for sound are never loaded, even when you enable sound later. I would suggest we just remove the check completely which will fix part of the long standing bug and also fix the issue you have with return value check for the read_actor_defs() call failing too. Edit: Perhaps safer for now, leave the have_sound_config and return 1 to just prevent the error. I'll check some more later, but what do you think?
  5. Can't log in - The rules.xml file was not found

    I just tested again and it works fine for me. Sorry to ask but, are you sure you were pointing at the new libxml2 headers when you compiled? If the conditional compiles is not included the higher threshold will not be set in actor_defs.c. Everything will compile but the defs will not load. #if LIBXML_VERSION >= 21200 xmlCtxtSetMaxAmplification (ctxt, 100); #endif You can also test the library is working using xmlint: $ which xmllint /usr/local/bin/xmllint $ cd ~/eternallands/actor_defs xmllint --noent actor_defs.xml actor_defs.xml:143: parser error : Maximum entity amplification factor exceeded, see xmlCtxtSetMaxAmplification. &elf_female; $ xmllint --noent --max-ampl 100 actor_defs.xml ... outputs the expanded xml
  6. Can't log in - The rules.xml file was not found

    That's the commit version I tested with of libxml. Can you confirm you are using the correct library at runtime? On Linux that would be ldd on the binary.
  7. Can't log in - The rules.xml file was not found

    I've tested the new version of the library (2.12 not yet released) and using the new ability to set a higher threshold does fix the problem. I've committed the change but stick with version 2.10 of libxml2 until 2.12 is released. Version 2.11 will never work and I've made compiling against that version fail.
  8. Can't log in - The rules.xml file was not found

    The issue I logged has been looked at and the libxml2 devs have already made a change that should allow us to fix our issue. The actor defs are tripping the new "Protection against entity expansion attacks" and the change is to allow setting a higher threshold. I'll test it tomorrow and report here. https://gitlab.gnome.org/GNOME/libxml2/-/issues/581
  9. Can't log in - The rules.xml file was not found

    It could be. I've tried looking at this but I have no idea when its needed. Adding it to the top of the actor_defs.xml does parse, but we still get the error. I've created an issue on the libxml2 repo. We may get some pointers there: https://gitlab.gnome.org/GNOME/libxml2/-/issues/581
  10. Can't log in - The rules.xml file was not found

    I've been trying to fix this for a while now but so far unable. As I said above, I think there may be more than one issue. I've committed the possible fix for reading files but actor defs still fail to load. I added proper detection of this and a pointer to this thread in the error logging. I'll keep trying but help from someone more familiar with libxml2 would be great. I may create an issue on their bug tracker but suspect its and EL problem.
  11. Hatwood

    Very sad news indeed. She was very active in LNX guild for a while, made it a fun and pleasant place to hang out and always a pleasure to talk too.
  12. Can't log in - The rules.xml file was not found

    The 2.11.x series of libxml2 has new protections for "entity expansion attacks" which we appear to be triggering with the el xml files. I'm looking into this but cannot find fix a solution so far, it will hit us eventually on other platforms, not just arch based. There is also a change to the way custom loaders work with libxml2 that triggers another issue that I have fixed (I think). Building a static binary unfortunately requires a lot of work as you need to build all the libraries yourself making static versions. I have scripts to do this and still intended to publish them to my EL build methods repo once they are cleaned up a bit. There is a flatpak package that works on Arch and Manjaro, and other distros, available in the flatpak store. I publish a development version too (needs updated to the latest git) that you can install by enabling the flatpak beta channel.
  13. Can't log in - The rules.xml file was not found

    Definitely not wasting time. I was testing using one of the package builds which works. But if I compile my own. I have the same problem with the new version of libxml. I'll look into why that is in case its something we're going in the client that is no longer supported.
  14. Can't log in - The rules.xml file was not found

    Looks like its opening. Perhaps the xml parse fails. Do the contents look OK? This is my checksum; md5sum languages/en/strings/console.xml b635aa251c0d017e095fba0cc3118bca languages/en/strings/console.xml
  15. Can't log in - The rules.xml file was not found

    Perhaps you could try using strace to see what's happening: strace ./el.x86_64.linux.bin.static 2>&1 | grep console.xml You may need to install strace.
  16. Can't log in - The rules.xml file was not found

    If you assume the client is looking for the files in /home/sb/el_linux can you check one of the errored files exists and is readable by the user you run as? The client looks at various system folders for fonts, I assume that's why the conkeyxy files show in the low.
  17. Colour GM messages

    The console background is a texture so can be changed reasonably easily. It might help if you lighten the darker parts a little. I tried a flat (for simplicity), but lighter texture and its arguably better IMHO. Too light though, and the colours get washed out and you start to see the font outlines. The file is textures/console.dds in the data directory. As always, save a copy before changing it.
  18. Fixed in git. Still limited support but now includes "Latin-1 supplement" as supported in EL.
  19. That's good. It was nice to contribute something again, its been a while. As revi said, you'll have to build you own client for now unless someone provides one for Mac. I do not have a way to build on Mac but Ben has provided build instructions on Github.
  20. I've just committed a change to add an option for a food level bar (ALT+y) and numbers (CTRL-y) as part of the player banner. With dynamic colours enabled, the bar is yellow when full and moves to dark orange when empty, otherwise is just yellow. Let me know if this is what you wanted, I'd be happy to change the way its done otherwise.
  21. first use

    It could be your ISP is blocking port 2000. Can you try connecting using telnet? You should see something like this: $ telnet game.eternal-lands.com 2000 Trying 192.99.21.222... Connected to game.eternal-lands.com. Escape character is '^]'. G�Welcome to the new server! Please report any problems on channel 6. On second thoughts, if you got as far as character creation, you already connected to the server. I assume you are still using the default server not trying to connect to one of the SSL or proxy servers as those no longer work.
  22. Unable to connect to server

    It is likely something that's changed your side. Did you install updates around the time? Have you changed your firewall setting?
  23. I made installing the music the default for all the packages I produce except the Ubuntu/Debian packages, for which its always been an optional dependency. Next time I do a build of those packages, I can change that too.
  24. Chars getting whited-out

    Some unused options were removed from the last Android client to declutter the options window. Shadows was one of the removed options so it should already be effectually doing what unchecking the trouble shooting option does. Poor_man disables a set of options so you could try these individually to see which is "fixing" the problem. I suspect its the eye candy. Poor man turns off these options, I've striked-through out those already disabled on Android: show_reflection= 0; shadows_on= 0; clouds_shadows= 0; use_shadow_mapping= 0; special_effects= 0; use_eye_candy = 0; use_fog= 0; show_weather = 0; use_frame_buffer= 0; skybox_show_clouds = 0; skybox_show_sun = 0; skybox_show_moons = 0; skybox_show_stars = 0;
×