bluap

This change is included in the updated client available from the 1.9.6 update thread. Grum did the work.

Using telnet would not resolve the issue but just test if you could connect to the server The command is this, telenet <domain> <port> telnet game.eternal-lands.com 2000 When run from a terminal, I get this output: 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. <Ѳr� The "Welcome to the new server!...." bit shows that I can connect to the main server OK. If you do not get that text, there is a problem with you connecting to the game server that is not due to the client but that is likely due to your ISP. Again, connecting to the test server would not correct the problem, it would just prove that the game is working on your system and the problem is likely access to the main game port, 2000.

It looks like you are getting past the font set-up, the font errors are just fonts that cannot be used by the client. It look like you are posting the output from the Ubuntu packages launcher which only happens after a crash. If its a lock up, are you forcing the client to terminate to get that output? What is the last loading message displayed before it locks up? Have you tried connecting to the test server?

Do you have anything in the latest log file? ".../Eternal Lands/log/main_<random characters>.log" There should be a line including "....reflection.c:..."

Which platform are you using. I mistakenly posted the information a few minutes before I uploaded the windows zip files, the version number should be 1.9.6.0-20220121. Grum did the fix and it works for the systems we tried it on that were experiencing the problems. I'm sure Grum would like to hear from you.

Another update, please see the top of the topic.

Glad you got it sorted.

Its the same code on Android and the desktop client, 15 characters the maximum for both.

More new bug fix builds, see top of thread. If you have had issues with settings and received the message "Problem with <file type>" then please install this update. Someone helpfully reported that when they received the "Problem with <file type>" message the file was zero length. This is now detected and logged to the console. The error no longer prevents the file from being saved. There is now additional logging (including console messages) if there is an issues when saving a file. To do this, an explicit close of the file is now done and there is a possibility that this may fix the "Problem with <file type>" issue. If it does, you may see the "zero length file" message once, but not a second time for the file. If you do get the "closing file failed" message, please report the issue to the forums and include the contents of the last log file "<user settings>"/logs/main_XXX.log".

I've fixed the problem. It would have worked after using #glow" three times too. Anyway, I'm going builds for this and other fixes currently and will posit in the main thread.

OK, that's the first time I've seen that reported. I'll look at fixing it.

I've just tested and it worked fine for me. As on the desktop, I note you only get the message if you have the perk though. It's a server #command so nothing really for the client to do.

Updated build (2022-01-09) with additional small fixes and improvements list at the top of the thread.

I like those suggestions. For now, you can already double click the message area to clear the text.

So you noticed the leopard kills were missing before you exit the client after doing the daily? As Learn said, some kills get missed occasionally but missing all of then is unlikely. Sorry, I do not know why that would happen. The code involved is unchanged in a very long time.

Did you start another client at the same time and login with the same character (causing the other to disconnect)? The counters are saved on exit, on #save or periodically with the background #save equivalent. If you had started a second client and logged in with the same character, the last one that saved would be the one that matters.

If the degraded item is not showing the correct image (reversed and with and !) then it should get fixed with the next server restart. It's because we updated the image ID in the client data but that changed did not get included in the last server update. The image, the hover-over description and the equipment swap all depend on having this information correct.

For the 1.9.6 update, I noted quite a few people had issues with the key.ini file so I thought I'd document the following: The location of the key.ini file (unchanged since forever): The default version of the key.ini file is located where you installed the client; the client data directory. Modifying this version in place is not recommended. Like all other files placed there by the installer, it will be overwritten when next you install a full update. Instead, copy the file and put the copy in the top level of your personal settings folder. Files in this folder will never be overwritten or changed when you install a new client. On windows, your personal setting folder is usually "C:\Users\<your login name>\Documents\Eternal Lands\" on Linux this is normally "$HOME/.elc/". Note, this is not the location of many of your other personal files which are in a sub-folder of this such as "main". On start-up, the client writes a message to the console telling you this sub-folder location. Just move up one folder from there to get to the top level of your personal settings. The client looks for the key.ini file in several locations, stopping when it finds the file. The sequence of locations checked is this: 1) Personal Folder top level, 2) Personal Folder "/updates/<client version number>/" and 3) Installed data folder. In each of the locations, the client will also look for compressed versions with the ".xz" then ".gz" extension. Changes since client was updated to use the SDL version 2 library (1.9.5p6): The left and right CTRL/ALT/Shift modifier keys are now independent. If you use LALT for your definition, RALT will not work too. As before, you cannot define a second key for the same action and if you do, only the last definition in the file will work. The key definitions (other than modifier keys) use the Key Names specified by the SDL2 library. This is largely as it was previously with the notable exception of the keypad keys. Also, if the Key Name includes a space, then you have replace the space with an underscore when adding it to the key.ini file. For example, to define #K_SPELL1 to use keypad 1, you would add the following line to your key.ini file. #K_SPELL1 = KEYPAD_1

I have the invisible actors problem with Nvidia too, but if I restart the client with UVP it works fine. I normally have UVP off as it makes the characters eyes look weird (another bug I've not been able to fix). Has the problem with water always been the same, in particular pre 1.9.5p26 when we moved to SDL2?

Going forwards my intention is to release development versions that can be installed over the Play Store version. Previously these development builds have used the id com.el.elc, the Play Store version uses com.purebinary.elc. This difference meant that if you installed both builds, you would have two versions installed each with separate user data. I think shifting to a single version based on the Play Store id is the best way forward. If you are using the previous com.el.elc version please remove the app, install the Play Store version then side load updates from here if you want the development version. Anyway, I've done a new development build 1.9.6.0-20211228.1456. Changes include (most not just for Android): An option on the video tab to set allowed screen orientations. I will continue to look for a way to use device settings instead. Fixed display of action point > 999 in the stats window. Correct colour for login window version text when there is an error. Enable item user counters always now we cannot run old clients. Add chat channel colours window to managed windows; enabling auto scaling. Change ground bag window default position to bottom centre. Fix blank lines in console when wrapping text to fit width.

Good news.

That comment was for Andy_c!

Did you remove the old app before installing from the store? Have you tried clearing the app data? Note these both steps will mean you loose your user data.

There has always been spacing between the HUD icons on Android. I know fitting the icons is a big problem for portrait mode on most devices and I'm considering what can be done. In landscape mode the initial-run scaling usually works OK. You could reduce the UI scaling a bit until it fits; change the "User interface scaling factor" option on the "Fonts" tab. I'm also considering detecting this issues and adjusting the initial-run scaling.

When you say the old version was working, do you mean the old play store version or the development version discussed in this thread. Also, is the initial login screen black of just when you log in.