Cabman

I personally don't agree with having these pots at all unless they do not stack and have a very short time limit. A pure fighter build (assuming no bought nexus throughout) has 7 or maybe 9 PP in nexus. An all arounder has 20+ (I personally have 26) and most still need to move nexus around to complete quests. In particular the tutorial quests (manu, crafting, eng) were designed so that the maximum nexus is needed about 1/2 way through. Those that choose a pure fighter build know that they can't do these quests, and that is their choice. As well as most of the nexus (nexii?) above a certain amt are only required for very specialized items. So why should someone who chose a specific build now be able to mix anything at will, complete all quests, etc., while still having the luxury of better stats than someone who chose an all arounder path? If the pots are limited to short duration and are unstackable, well we have nexus transfers for that. I'm personally sitting on a bunch so I can finish certain quests even though I have nexus to make 90% of the stuff in game. Let ppl use transfers. That is what they are for. My 2 cents....

Screenie from my Nexus 10

Still out.....

I searched, but didn't find this.... I noticed a lot of crit fails while summoning on the last Summoners Day and think it would be a nice idea to have summoned crit fails listed in the counters along with the other mixing crit fails. In my opinion "xyz Failed - Ingredients Lost" when using the manufacture window is always a critical fail.

A couple of problems with this whole process: Firstly: This was not what the original post said. What was said was: A minimum gear set was proposed and initial voting was based on that. Subsequent to criticism, the minimum gear requirements were changed in the first post, yet I don't see any notification of an edit in that post. Secondly, I don't think the problems with invances are the same across all different ranges. Modifications to the gameplay (if they are required) should not group the 50 a/d with the 150 a/d. They have different goals and different styles of play. I posted my comments about the 40-60 & 60-80 invances in this post, http://www.eternal-lands.com/forum/index.php?showtopic=57405&st=20&p=568909entry568909, and I stand behind it. When asked if in general I think that invances should have minimum gear requirements, I would respond "probably yes". But I cannot agree to ridiculous gear requirements for low lvl players. It will simply kill the lower level invances if players are scared to go (or can't go) based on their gear and the fear of repercussions from the moderators. Whether you should "help", that is a given, and already covered by the rules.

I voted NO for the gear requirement. Requiring 220kgc in gear minimum for 60-80? Might as well just not run them....

Firstly, I can only speak about the lower lvl invances (40-60 to 80-100). From the discussion in numerous threads, I believe the 100-120 & 120+ have their own problems and dynamics and that anything that is modified needs to take into account ALL the invance levels, not just addressing the problems of the higher lvls. 40-60 & 60-80 Armor & Weapons: "Run what you brung" Ranging: PK arrows Participation: Kill what you can! At these levels, no one should be forced to grind to aquire top armor and weapons before being allowed to invance. I see these lvls as a learning experience for group tactics and dynamics. There are a lot of deaths and it simply isn't practical to expect those players to risk months of hard earned gc. There are also a huge number of lower level mobs that can be engaged by those at the lower end of the range, allowing them to help the group immensely, even if only wearing augs and brandishing an iron sword. Even at the top end of the range, most do not have no-fail and MD, so the boss mobs are still tough, but are usually well handled by the better equipped and better experienced players. Gate protection is a necessary job, and 3-4 lower levels milling around the gate can usually protect the gatekeeper until the higher lvl fighters can respond to help. I don't find this offensive as it allows the others to go out and sweep the map once the mobs near the fort have been cleared up. The biggest problem at these levels are people who come to purposely do as little as possible for the exp and those that come to BJ, fleeing mobs, etc. Making BJ'ing in these invances a banable offence (invance-only ban or game ban) would solve 99% of the problems. 80-100 Armor & Weapons: Decent armor and sword (augs for rangers is fine) Ranging: PK arrows Participation: Kill what you can! At the 80-100 range, gc is easier to come by, so decent armor and weapons are not much of an issue for players and any exceptions to this are usually handled by the team itself (new invance players who only have steel chain, etc. happens occasionally, and are normally welcomed for their participation as we all like to see new people coming to invances). Others can be handled through the existing #abuse system. Until the upper level of the range, alot of the mobs are still very hard to kill. Low 80's a/d can't take being multied by clops and fluff and MCWs are hard to hit at all levels even with the multi penalty. There are still a lot of lions, hawks, clops, etc. that can be taken care of by those without top gear and lvls. BJ'ing at this lvl & above is fine as long as people don't sabatoge. If you don't want to lose your gear, bring a rostogol stone. That's what they are for! AFK'ing is already handled in the current rules, and I don't see much of it at this lvl. Again, the #abuse command works. Cabman

When harvesting, I noticed that the framerate has a significant effect on the density of the particle animation effect. At FPS limits of <60, a dense particle shower is seen. At max FPS for me >250, almost no animation is seen. Switching to console and back produces a 1 time flurry of particles. I'll try to upload some screenshots. Hardware is NVidia 580 Ti. Linux ubuntu 3.2.0-27-generic #43-Ubuntu SMP Fri Jul 6 14:25:57 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux NVidia driver 302.17 Xorg 11.0