Jump to content
Eternal Lands Official Forums

Burn

Members
  • Content count

    1177
  • Joined

  • Last visited

Posts posted by Burn


  1. (1) MN gets angry more often, *5 damage.

     

    Means in-game: Most likely rarely harv again, then with a CoL and load of HEs at all times. Assuming includes all painful harv events like radon, which would cause 150 damage per hit like this.

    Good for: People who buy the majority of ings instead of harv? No regular harver would take this.

    Gain: 3 pps to make harving impossible on bad astro days permanently. When seen that way, 3 lousy pp's aren't worth it. (This is the ICD/Gele bones of harvesting combined and worse. Look at the points gotten for those)

     

     

    (2) Permanently pk-able

     

    Means in-game: You'll never manu, harv, or anything else for that matter again because bored kids will be attacking you on sight just because they can. You're essentially on the pk-server except without the ability to attack others, just the other way around. And people will. Spend the rest of your days in the UW, no means of earning gc to regain equipment lost/damaged/destroyed on your first day of the perk.

    Good for: noone. Guaranteed game killer. Forced reset.

    Gain: 5pps that won't make a difference. (Anti gives 10, this kills your game completely for 5?)


  2. VaMpIrEsIxTeeN changed name, is now bLaCkBiRd. (showed up at votd sto wearing exact same gear as I saw her last as vampire, has the exact same stats as seen on vampire before that name was deleted, and I wasn't the only one at sto that recognized her, hehe. Did an absolutely horrible job of trying to pretend to be someone else.)


  3. Prices would not go up because 1 place in the whole game is charging

     

     

    (So soon after) KJ got essentially shut down as an iron source, miners there moved to EVTR, yes, it would. Those "1 changes" add up in the long run, but add up drastically done so soon after each other.


  4. How I set it up (in case it helps someone):

    1- (superuser) Made a backup copy of /usr/share/games/elc-data (in case I had to revert back to 1.7) - Loc of your elc-data may vary.

    2- (superuser) Copied the zipped files into the above directory allowing overwrite all. (Zipped files are updated only files, not all the data)

    3- Set the binary to executable, and ran it (doesn't matter where the bin is located)

     

    Got illegal instruction on original binary, but I expected that since I got the same with 1.7 binaries. The "Duron" binary (which isn't just for Duron machines, if it works use it!) worked though.

     

     

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

     

     

     

    As for testing, gotten about 7-8 hours of play in with 1.8 now. Harved, map walked, fought a bit, mixed, traded with bots and npcs, tried out new stuff like equipment swap and new inventory buttons, and so far not seeing any problems (other than map issues that I know are awaiting a server update).


  5. I realise this is a bit off topic but whats the problem with Duron's?

    If an architecture specific kernel is being used, it's still the same as what would be used with an Athlon, AthlonXP or Athlon64 (when running in 32bit mode)... being a K7 optimised kernel... afaik, technologically, a Duron is just an Athlon-Thunderbird or AthlonXP-Palomino with less cache (please correct me if that's wrong)... how can there be a nVidia drivers or EL binary problem with Duron's but not with other AMD K7 family CPUs?

     

    Not just Duron* but any CPU that doesn't have SSE support. The 100.14.19.x Nvidia drivers was the last driver series to support non-SSE CPUs, and they are no longer updating those. There's no Nvidia driver available that'll work with the most recent Linux kernel for non-SSE CPUs.

     

    *clarification: 1st generation Durons (Spitfire) are what I'm referring to. 2nd gen Durons (Morgan and on) were the first AMD CPUs that included SSE. (Yup, my comp is VERY old!)

    http://en.wikipedia.org/wiki/Duron#Duron_core_data


  6. What CPU do you have?

     

     

    AMD Duron with OpenSUSE 11.0.

     

    (Not sure it's worth fretting over though, NVIDIA no longer provides drivers that work with this CPU combined with newer linux kernels, can't even use OSUSE 11.1 with this graphic card. Problem may shortly be obsolete.)

     

     

     

     

     

    EDIT: The i586 build works fine here. :hiya:


  7. "Illegal Instruction"

     

    I got that with 1.7 binaries as well though, so I'm not surprised. Very old comp here with graphic card that is just strong enough to handle EL. :hiya:

     

    I tried though. :) I'll have to do a self-compile later just as I did with 1.7, no biggie.

     

     

     

    ADDED (since new posts made while I was writing): OpenSUSE 11 w/ Duron CPU here, NVIDIA GForce FX 5200)


  8. Situations like this can and do happen in most any guild. That he was immediately removed from the guild is the best and only thing a guild can do when it does happen. Predicting future behavior of a player with no previous "record" is hardly something that a guild can be held responsible for.

     

    This situation could happen to every single guild in the game, not just CIAN. Don't think it couldn't happen to your guild as well.

     

    This was one individual player's bad behavior. The guild took appropriate (and immediate) action to show they don't tolerate it. Let's focus on the player, not the guild.


  9. Seen a few minutes ago again still trying to sell CoL on market. Kicked from guild, definitely seen thread (reason kicked), and still continues behavior.

     

    [VaMpIrEsIxTeeN @ 3]: Selling crown of life, pm me pls

    [VaMpIrEsIxTeeN @ 3]: Buy 1 Gelatine Removal Stone, pm me pls

     

     

    Blacklisting well earned.


  10. Waste another hotkey? Not sure that should be dignified with a response. It's a simple solution you chose to toss away with a useless word like "waste" when the combinations that could be used are far from running out.

     

     

    Common sense: Not every mouse is perfectly sensitive, or a hand-slip can move the mouse further than was wanted. Tell me you've never accidently clicked anything ever and I'll call you a liar.

     

    Your insensitivity that some people playing may also have physical issues that would cause such accidental clicks is... sad.

     

     

    Another program opening forcing system crawl while it does is the HUGE difference between being able to recover from an accidental click or not.

     

     

    It's piss-poor design to make it that easy to accidently open another program, at any time, period, and not just in EL. Especially from, like any other 3d program, a heavy-resource program. I'd wager that there's quite a few people playing on systems where running much of anything else while the game's on is not an option. Just because your system isn't doesn't mean they/we should get the shaft.

     

    You're begging for complaints over something very few people will ever actually use, that reason alone should keep it demoted to the keyboard. People who visit the site regularly have it bookmarked, where it won't be accidently clicked in-game. Even people who would use it, would likely only use it once at most during a gameplay.

     

    On-screen items should be limited to things that actually get regularly used.

     

    I'll completely ignore your last sentence, as changing the subject is only done when you run out of real things to say.

     

     

     

    If it "must" be implemented, [x] option, OFF by default. The key part of that being the OFF by default.


  11. If this were implemented, that wouldn't be an alternative but the only option.

     

    There should never be anything on screen that if accidently mouse-clicked at any time would force another program to open. That's poor design. Your nice computer, perfect mouse, etc., might not have a problem with it, but those of us who can't afford such luxuries are the ones who will get screwed by this idea. It is guaranteed to lead to complaints. People accidental-click things all the time, this won't help that.

     

    Again, nothing against an easy access to the site, but move it to the keyboard.


  12. Sorry, but forcing people to change their gameplay method for a link is not an improvement. I shouldn't be forced to use two hands when used to one over a link, nor should anyone else.

     

    It's not just fighting, it's mixing (always have FPs in the top slot), etc. Much of which is done one-handed, your suggestion would change that.

     

    Your method of play is not my method of play, do not attempt to destroy my method of play just because it's not yours.


  13. You're fighting, emergency, restore quick! Rush the mouse up to click the Restore at the top of the quick bar. Mouse went too high, click the logo instead. Game crawls as that accident causes another program to open. Oops, you're dead.

     

    Just one example.

     

    Quick access to the site sounds good, but having it that close to things that are regularly clicked during gameplay -making it an easy target for accidental clicks- is a Very Bad Thing.

×