Jump to content
Eternal Lands Official Forums

Search the Community

Showing results for tags 'client'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Official
    • News of Game Updates
    • Rules
  • Help and Information
    • Help Me
    • Bots
    • Bans
  • Game Topics
    • General Chat
    • PK Server
    • Events
    • Skills
    • Marketplace
    • Guilds and Clans
    • Disputes
    • International
    • Stories
    • Off Topic
  • Development
    • Suggestions - General, Misc.
    • Bug Reports
    • Programming
    • Map making
    • Encyclopedia

Calendars

  • Events Calendar

Found 6 results

  1. Introducing the brand new 64-bit Eternal Lands client for the Mac! The client is compatible with macOS 10.14 Mojave and onwards (yes, we finally have a client for 10.15 Catalina!), and for the first time ever has been both signed and notarised by Apple to ensure it’ll run without any compromises. This client also introduces a beautiful new High Resolution mode for Mac users with modern displays. High Resolution mode is automatically detected and enabled for systems which support it, but does use slightly more resources. If you’d rather forego the beautiful crispness in favour of performance, you can disable High Resolution mode via the method described here. As of 1.9.5p8, the macOS client also includes the minimal BurnedMaps pack by default, eliminating the need to install it separately. If you'd prefer to use an alternative (such as the full BurnedMaps pack), please follow the instructions here. Moving forwards, updated Mac builds will be made available regularly alongside those for other platforms where possible - keep an eye on the download link below or the general chat forum for new releases. Big thank you to Bluap for all the hard work he does to bring us new features, and to VinoVeritas for assisting with bugs and testing - you guys rock! Download Here (Eternal Lands macOS 1.9.5p8, released 30/4/20) Previous Version (Eternal Lands macOS 1.9.5p7, released 22/4/20) Any problems or questions? Please read the Eternal Lands for macOS FAQs first.
  2. Eternal Lands for macOS - FAQs

    Welcome to the Eternal Lands for macOS FAQ! Contents: My FPS is lower/My Mac is noisier/How do I disable High Resolution mode? How do I open more than one game client? How do I access other servers? How do I install custom maps? What if I am running a version of macOS older than 10.14 Mojave? Have a problem or question which isn’t covered in this FAQ? Feel free to contact me (Ben) in-game for smaller issues, but otherwise please post a detailed description of your problem in the Mac forum along with the following information: Your EL version (you can obtain this by typing #ver in-game, or viewing the app's Get Info window) Your macOS version and Mac hardware type (both of which can be obtained from Apple menu > About This Mac) Non-mac-specific issues should be directed to either #help_me or the appropriate sub-forums as usual.
  3. I've been working on a new way to build the windows client which is now ready to test. I'm using a tool-chain called MSYS2/MINGW which allows use of the latest compiler and up to date libraries on Windows 10. This all means that the resulting executable should run better on Windows 10. I have also automated the build process and so can provide more regular test clients for Windows like I already do for Linux. The previous builds I have provided were built using a very old tool-chain on Windows XP; which was not good. Please give this new build a try and please give me some feedback. But, BACKUP your current el.exe and all the .dll files before installing the new package as these files will be over-written by the package. Also as always, ensure your important game files like your quest log etc are backed up; good practice even if you do not try this new client. The packages only contains the el.exe and the required .dll files, the game data is not included. There is a 32-bit package and a 64-bit package for Windows 10, extract the zip archive for your version of Windows into the game data directory where the existing el.exe and .dll file (which you have backed up) were located.
  4. Since I like to catch up on email, websites, etc. while harvesting, and generally like to have audible warnings for numerous events if I'm in game but Away From But Near To Keyboard, or get distracted by doing jigsaw, I have a great number of client alerts defined, up to 26 sounds, now. However, I can't seem to get _all_ of them to work, only about the first 15, so my question is: is there a numerical limit to how many sounds can be defined, or do i have to look for some other obscure error I have made?
  5. Developer client - Windows

    How do I get the developer client for Windows so I can change font colors and stuff like that?
  6. Improving mouse UX

    Hi, all. I'm relatively new to the game. I'm an experienced software developer (though I haven't worked with C or C++ in years). I've spoken with radu about my idea, and he suggested I post in here to get some feedback and discussion about it. Among several other improvements I want to try to make to the client code, I want to try to improve the mouse clicking user experience. Specifically, it seems that clicking (and the results of clicking) in the main world view window operates on an "exact pixel" basis. For example, you must click on one of the pixels of a flower to begin harvesting it (based on the current camera angle). At wide zoom amounts, this can mean very few pixels to click on. Trying to initiate combat with things like bunnies and brownies is significantly more challenging (frustrating?) than attacking large creatures like deer. What I'm thinking is to just expand the code to consider an n by n square of pixels (or perhaps circle) around the mouse cursor, instead of just one single pixel at the mouse cursor. Then have the cursor operate just as it is now (including both hover and click functionalities), except the thing hovered over, or the thing clicked is the one that is closest to the mouse cursor within this pixel area. When there is more than one small hotspot near the cursor, the UX will still remain as tricky to use as it is now, but if you are trying to chase a bunny down, and there's nothing else in the vicinity, this change should make it much easier to do so. Any thoughts on this approach, or tips on where to start? I've only briefly browsed the code, but I've found such things as thing_under_cursor. I'm also thinking that this should be a toggleable setting, as it is likely to require a little more CPU power.
×