Jump to content
Eternal Lands Official Forums

squiz

Members
  • Content count

    60
  • Joined

  • Last visited

Posts posted by squiz


  1. 19 hours ago, Aislinn said:

    Did you check your config file for whatever your window manager is?  I had the same problem (couldn't use alt key to easily get the item to storage) and it turns out that the alt key in openbox was bound to a few things I never used.  I just removed those entries.   My file location was /home/sb/.config/openbox/rc.xml   (Arch linux).

    Thanks Aislinn. I am using LXDE, which uses openbox as a window manager. in my file ~/.config/openbox/lxde-rc.xml I commented out the following under <mouse>:

     

    <!-- eternal lands
        <mousebind button="A-Left" action="Press">
          <action name="Focus"/>
          <action name="Raise"/>
        </mousebind>
        <mousebind button="A-Left" action="Click">
          <action name="Unshade"/>
        </mousebind>
        <mousebind button="A-Left" action="Drag">
          <action name="Move"/>
        </mousebind>
    -->
     

    This fixed it. Alt-LeftClick works now.

     


  2. Clicking Alt-LeftMouseButton on an item in the inventory is supposed to put all of that item to storage. This doesn't work on my system with the standard Alt key to the left of the keyboard. Instead I have to click the AltGr button, which is to the right of the spacebar on my German keyboard. Strangely Alt works for other commands, such as Alt-s sit/stand.

     

    I had a look at the key.ini file, but can't find any likely settings that might affect this.

     

    System information

    I am running on Debian with the package version 1.9.5.8-15debian1. 

    The setxkbmap command gives the following:

    setxkbmap -query 
    rules:      evdev
    model:      pc105
    layout:     de
    variant:    nodeadkeys
     

    I have not altered my key.ini settings.

     

     


  3. Could someone tell me what the maximum a/d penalty is for TS pots? I took a few pots and got the penalty 3 times, but my a/d was reduced by only 8. I seem to recall reading that you could reduce it more. Is that true, or has it changed?


  4. I have the harvesting effect enabled.

    After a network disconnect while harvesting and then a re-connect, I sometimes notice that the harvesting effect keeps on going, although I am no longer harvesting.

    When I then start harvesting, the harvesting effect stopped.

    When I then stopped harvesting, the client crashed.

     

    This, or something similar, has happened twice so far.


  5. I see that 1.6.0 final has now been released in binary format, but has not been tagged in CVS.

     

    I don't want to appear to be complaining, or overly fussy, but might I suggest that greater use is made of CVS tags or labels. In my experience, it is a great help in knowing exactly which version you are testing on. As a linux user, if I wanted to test a particular RC, or switch between RCs to track down a particular bug, I would have to try to guess when the RC was built and get cvs from that time.

     

    It is a bit late now, but I think every binary release (that means RCs and not just full releases) should also be tagged. There is very little overhead or effort in doing so and the advantages are that you can always test with a defined state.

     

    Anyway the final release should at the very minimum be labelled.


  6. I would like to test this in linux too, which means that I have to compile from CVS. As there you have not tagged this test release, it would mean that I would have to test against HEAD, which currently seems to be quite a moving target, with lots of new features.

     

    Would it be possible to tag such test and bug-fix releases in future? That way we could at least build to a defined state.

×