Jump to content
Eternal Lands Official Forums

Burn

Members
  • Content count

    1244
  • Joined

  • Last visited

Posts posted by Burn


  1. FTR: "Holes" as well as start-stop or breakage of mapwalking are caused SOLELY by not having the same map in your client as the server has.

     

    That they exist is in itself the proof that your client is using 1.9.4 data for some reason on the 1.9.5 server.

     

     

    A hole: the server has that particular tile as walkable, but since your old map doesn't - you can walk on it because the server permits you, but your old map has no information on what height you should be at because it has it as unwalkable. "unwalkable" in map terms is actually a height positioning lower than the lowest you can be in the game, so you end up "in a hole".

     

    Stops during mapwalking are due to the exact opposite, the client has walkable tiles that the server doesn't, so you stop when you get to those tiles.

     

     

    The solution in both cases is to get your client working with current data.


     


  2. Just a few things you won't really notice unless told, or you study my tab maps like a maniac... these are "little things" besides those already listed in radu's client update notice.

     


    C1

    - VotD - The southeast fenced-in area (where Gerund is) can now be used as a manufacturing school

    - VotD - The tombstone closest to KF (18,121), "eye" it for a dedication to Pookies.

    - TG MS Garden - One now-enterable place that you couldn't enter before.

     


    C2

    - Glacmor - One previously unenterable cave can now be entered (just a small insides)

    - Hurquin - Two previously unenterable buildings can now be entered.

    - Hurquin - The "Chapel of Knowledge" building inside the cave is now fast reading.

    - Irinveron - One previously unenterable building can now be entered.

    - Irinveron - The huge cave I add last time now has a second way to enter it, that is from a different map (so if it's invaded, you can enter there for the 10-second delay before attacked)

    - Idaloran Mine - The 2 "pit" PK areas have been adjusted so the entire pits (down the ladders) are pk, parts weren't before. Safety only by leaving the pit. As well, the northwest "bad air" pk area now covers the full dark brown dirt area, instead of just a random spot in it. Safety outside of the dark dirt.

    - Melinis - Summoning Academy - In the main hall, is a new dragon statue, "use" it to see a dedication to Bromber.



    Other
    - Dung Portal - Due to Zirak changes, one of the Zirakinbar drop locations now drops in North Zirakgunda.

     

     


  3. How do I know I have 1.9.5 installed?

     

    - Go to 372,112 in Idaloran. You should see a new huge palace there.

    - Go to 196,47 in Zirakinbar. You should be at the door of a house (that wasn't there before).

     

    If you go to either of those places and you don't see what's written, you're seeing old maps which means you either have not installed the new version or you have an issue with your install.

     

    I have installed 1.9.5 but I still don't see the things in Ida or Zirak. What now?

     

    Most likely you have a personal el.ini file that is overriding the new 1.9.5 file and it is pointing to the wrong data (for some reason you still have the old version installed as well, get rid of that).

     

    linux: ~./elc/main/

    Win: \My Documents\Eternal Lands\main\

    Mac: ~/Library/Application Support/Eternal Lands/main/


    1- Turn off your client. *important to do first*

    2- Go to the directory for your comp.

    3- In it, you'll see an el.ini file. Just delete it, client will create a new one.

     

    That should take care of it.

     

    Why can't I see the new inventory images?

     

    This update is just the necessities to ensure the client is working. Other additions such as this will come once things are stable.

     

    Why can't I find the new storage NPC Tash in Zirakinbar?

     

    This update is just the necessities to ensure the client is working. Other additions such as this will come once things are stable.

     

    Why can't I see/find...

     

    You should see a trend in the answers here. Hop on that trend. ;)

     

    What are the hints given for the biggest new secret in the game?

     

    (1) This new dangerous secret is entered via another secret.

    (2) Bring radu's favorite object with you.

    (3) "YOU FOOL!  NOW YOU DIE!"

     

     

     

     

    OTHER KNOWN ISSUES

    - Idaloran Docks - The guild NPCs are facing the wrong direction, and 1 is even out of place. These are up for fixing in a near update.

    - BOT OWNERS - Do not use the automatic travel to storage and back. Log in to your bot and walk it there.

     


  4. When 1.9.5 gets released, some maps will be drastically different, others will be still tweaked and changed to some extent.

     

    Are your hyperbags safe?

     

    If they're on Ida (outside), or Zirak (inside or outside), or in the Grubani arena... there's a higher chance they aren't.

     

    Guild maps are always safe, they don't get touched.

    Instance maps will be guaranteed safe this time as well.

     

     

    If you can set up a separate system to use on Test, you can use the 1.9.5 testing client on the Test server, go to where your bag is. If you can stand on the coordinates of the bag there, it's safe.

     

    You're definitely okay if you can do that now. The maps on Test are the maps that will be on Main when the client update happens.

     

     

    But if you're truly paranoid, if you have any expensive stuff out in bags somewhere for some truly bizarre reason, just pick it up. If the maps update and the bag is on a then-unwalkable tile, it's gone for good.


  5. Actually, the list in the 1.9.5 data is pointing to the old images. It was made with a script I wrote that just rips the info from the file that the server uses, provided by Radu.

     

    I thought that went by object ID, not image.... so I didn't think twice about it. The images are updated using a file I edited for the server on Test, but the item list in the client was done with the main server's file.

     

    Not a showstopper, it's just trade log printouts. But yeah, that's not gonna change if it's going by image IDs.

     

     

     

    (Let's uh... let's make a pact that -assuming a 1.9.6- 1.9.6 gets rid of all uses of images for identification. Unique item IDs or bust. ;) )


  6. SEEING OLD MAPS?

     

    If you installed the above versions and are on Test server but not seeing new stuff, go to  /.elc/test/ and delete the el.ini file in it. (Or if you know what you're doing, change the #data_dir in it to where your test 1.9.5 is installed.)

     

    HOW DO YOU KNOW IF YOU'RE SEEING NEW MAPS?

     

    Go to 373, 112 in Idaloran. You should be standing between a new palace to your north and soldier barracks building to the south.

     

    If you're seeing plain grass and trees, you're looking at an old map.


  7. http://www.gm.fh-koeln.de/~linke/EL-Downloads/EL-MAC-1.9.5.zip

     

    Please test to see if the client installs and runs. Preferably on Test server as you will have problems using this on main.

     

    If you don't know how to install this seperately from your 1.9.4 client, be prepared to reinstall 1.9.4 as well for playing on main.

     

    Post any crash info.

     

    (Note that on Test server you have the correct maps, but the unofficial tab maps are unreleased for it so you'll have to walk around blindly in new or rebuilt areas.)

     

    Please also post if you found it works okay! Just so we know it's being tested.

     


  8. Ozu map seems to be the only one crashing in this manner. I've tested all other guild maps.

     

    It's not something at the entrance, either. I've tried mod-command teleporting into the map in various different places, all crash. So it's crashing with a general map loading. :-/

     

    Which is truly odd since it hasn't been changed. I could definitely enter this map back in 2014 (1.9.3).

     

    I'll look into it more, but honestly dunno what to do without knowing what is causing the crash.

     


    ---------------------------------------
     

    Separate note:


    I get occasional crashes when using the mod teleport command. This isn't the same issue as

     

    It's not common, but best I can tell it tends to happen when teleporting too/from areas that are of a laggy nature.

     

    Best place I could reproduce it was as such... teleport back and forth between

    25 150 10 (VotD near sto)

    200 100 153 (a guildmap spot that drops even my good computer down to the 20s in FPS)

     

     

    Worse, I crashed occasionally just walking around that area on that guild map. I didn't do that before, back in 1.9.3 days.


    The first error was most normally seen.


     

    *** Error in `/home/flame/el_linuxTESTSERVER/el.x86.linux.bin': double free or corruption (out): 0x000000000a94a580 ***
    
    ======= Backtrace: =========
    /lib64/libc.so.6(+0x721af)[0x7f7ee97c81af]
    /lib64/libc.so.6(+0x77706)[0x7f7ee97cd706]
    /lib64/libc.so.6(+0x78453)[0x7f7ee97ce453]
    /home/flame/el_linuxTESTSERVER/el.x86.linux.bin[0x415af0]
    /home/flame/el_linuxTESTSERVER/el.x86.linux.bin[0x415bc0]
    /home/flame/el_linuxTESTSERVER/el.x86.linux.bin[0x415a66]
    /home/flame/el_linuxTESTSERVER/el.x86.linux.bin[0x4c348e]
    /home/flame/el_linuxTESTSERVER/el.x86.linux.bin[0x4c357a]
    /home/flame/el_linuxTESTSERVER/el.x86.linux.bin[0x4c36df]
    /home/flame/el_linuxTESTSERVER/el.x86.linux.bin[0x4c3807]
    /home/flame/el_linuxTESTSERVER/el.x86.linux.bin[0x4d102c]
    /home/flame/el_linuxTESTSERVER/el.x86.linux.bin[0x4bd3cc]
    /home/flame/el_linuxTESTSERVER/el.x86.linux.bin(main+0x9b)[0x4bdce2]
    /lib64/libc.so.6(__libc_start_main+0xf5)[0x7f7ee97766e5]
    /home/flame/el_linuxTESTSERVER/el.x86.linux.bin[0x4101d9]

     

     

     

     

    *** Error in `/home/flame/el_linuxTESTSERVER/el.x86.linux.bin': free(): invalid pointer: 0x000000000514b2e0 ***
    ======= Backtrace: =========
    /lib64/libc.so.6(+0x721af)[0x7f52477811af]
    /lib64/libc.so.6(+0x77706)[0x7f5247786706]
    /lib64/libc.so.6(+0x78453)[0x7f5247787453]
    /home/flame/el_linuxTESTSERVER/el.x86.linux.bin[0x415af0]
    /home/flame/el_linuxTESTSERVER/el.x86.linux.bin[0x415bc0]
    /home/flame/el_linuxTESTSERVER/el.x86.linux.bin[0x415a66]
    /home/flame/el_linuxTESTSERVER/el.x86.linux.bin[0x4c348e]
    /home/flame/el_linuxTESTSERVER/el.x86.linux.bin[0x4c357a]
    /home/flame/el_linuxTESTSERVER/el.x86.linux.bin[0x4c36df]
    /home/flame/el_linuxTESTSERVER/el.x86.linux.bin[0x4c3807]
    /home/flame/el_linuxTESTSERVER/el.x86.linux.bin[0x4d102c]
    /home/flame/el_linuxTESTSERVER/el.x86.linux.bin[0x4bd3cc]
    /home/flame/el_linuxTESTSERVER/el.x86.linux.bin(main+0x9b)[0x4bdce2]
    /lib64/libc.so.6(__libc_start_main+0xf5)[0x7f524772f6e5]
    /home/flame/el_linuxTESTSERVER/el.x86.linux.bin[0x4101d9]

     


  9. There have been no subdirectories in /3dobjects since before 1.9.3 so the map is quite old. The e3d's listed are directly in the /3dobjects folder.

    Creating a /rocks directory and having the e3d in it didn't help.

     

    Though I suspect that in itself isn't the issue, as several old guild maps have bad objects like that but they still load fine.

     

     

    I don't recall doing a fix for this myself either... though I know I've visited that map before I started working with the maps and no crash. I've certainly not touched the map itself, it still has a 2010 datestamp.

     

     

     

    Are you stuck?

    If you're no longer able to log in, do the following:

    1- in you maps directory, rename guildmap_ozu.elm.gz to guildmap_ozu.elm.gz.REAL

    2- Rename testermap.elm.gz to guildmap_ozu.elm.gz

    3- Log in. You should be seeing a plain green grass map.

    4- Teleport, ring, beam off of the map

    5- Once you're off, rename guildmap_ozu to testermap, and remove REAL from the actual file to get your files back as they should be.

×