[April 12] Initial Development Manifesto Feedback
" Elitist elitist elitist. And? Reaction to picking up items? Rings any bell? It's supposed to be a competition, you compete against other exiles for the loot that is given. What about the people who want to play as a role of a thief? GGG has said that they don't like meta-options and this is just a beginning of a slippery slope that they unfortunately decided to walk. Whiners are never happy and satisfied, and now that they got this through, they will start the whine about other stuff, and it goes on and on and on and on... And before long, all those who don't want the game to go towards casual are gone, and then there's left only the whiners who will quit soon as well because everything that they whined about was implemented thus killing the game when trying to "appeal to all" (which is impossible). Last edited by mushioov#0149 on Apr 15, 2013, 8:54:35 AM
|
![]() |
The ranged versus melee disparity
When it comes to late game, all you really care about is 1. The time it takes for you to kill enemies (TTK) and 2. The level of relative safety in which you can do it. Now if you compare the skill gems (support and active) available to melee versus the those available to ranged, you'll quickly realise that the ranged active + support-gem combinations are so amazingly far removed from the ones available to melee that the #1 (time to kill or TTK) is not even a contest. The intent of multi-strike and melee splash is obviously a poor attempt at replicating the incredibly powerful chain / GMP gems, but it falls drastically short. Not only does it exacerbate the issue with physical vs. elemental damage, it barely closes any kind of significant gap between the TTK for a ranged versus a melee - maybe I'm being overly negative here, but I sincerely challenge you to show me a build where these gems are used in such a way that it comes even *remotely* close to the kind of TTK you can expect from the typical freeze-pulse, EK or lightning-arrow type builds out there. Ignoring the massive discrepancy between TTK for ranged v. melee, there is then the huge problem with survivability with melee. Monsters hurt. A lot. Regardless of whether you're ranged or melee! Ergo, it's a no-brainer to make melee characters more tanky; maybe this'll provide some kind of incentive to make up for the crappy TTK while you try to balance those half-assed melee gems you just introduced. What I would change if I had a magic wand +There is no reason why melee skill gems (I'm talking *true melee*, where you have to close enough to lick the sweat off the monster you're killing, not lightning strike etc.) shouldn't be significantly more powerful than ranged skill gems (increase effective damage on these skills by a large margin) - you want to be ranged and suffer no fear of death via kiting etc, fine - but your damage will not measure up to melee. Even if ranged have significantly lower damage than melee, their TTK will remain largely the same due to their vastly more competent ability to AOE crowds of monsters; this does mean their single-target will suffer in comparison, but honestly who cares, the benefit of not having to stand next to brutus to wail on him vastly outweighs the fact it takes you an extra 15 secs to kill him than it does for a melee; just chuck down another taunt-totem. +There needs to be a flat defensive buff to characters that are in melee range, using melee skills; how exactly, is up to you, but melee's never going to be desirable over ranged unless this happens. +Multi-strike: remove 40% less melee damage, and remove increased melee physical damage, leave the rest the same. (even then it's still not even close to how good chain is) "there is no spoone" - The Matricks Last edited by Zeekin#4930 on Apr 15, 2013, 9:12:28 AM
|
![]() |
I really don't understand the lack of action on the matter of lag/desync. Yeap, we all read the good words and the deep explanations why it happens, but what it all comes to.... other games have done it and it is working. Yeah, you can hate D3, but I have never had connection issues due to slow sync between server and client. Do not know how they achieved it and not sure if I would like to find out what corners they have cut, but it is done. Not all of us what to be tanks. There is no build diversity at all on the end-game.
|
![]() |
" Build diversity is in there. To understand true meaning of no build diversity -> play D3. :-) MY CHALLENGES ARE DONE ON HC, IT'S NOT SC GUYS!
|
![]() |
Melee vs. Ranged
My two highest level characters are a witch firestorm/summoner and a duelist. The witch, of course, has the easier time, especially with maps. The duelist was dual wielding, and I was having a very difficult time keeping him alive in latter act3/merciless or in maps. That has recently changed. The new melee support gems? No. It was to switch him away from being dual wielding to using a buckler and a single sword. It doesn't matter that I have less block now than I did with the dual wield, the difference in evasion alone is a tremendous help. I also have a marauder that has a 2handed axe vs. mace and tower shield as alternates. His survivability while wielding the two hander is substantially lower than when using the shield. Shields provide bonuses that weapons do not, bonuses that really make a difference in the survivability of the character. I would really like to see dual wield/2hander builds be more viable. I know people who do just fine with them, so I know there are viable builds out there, but they are much harder to accomplish that a sword and board fighter, and far harder than a ranged character. |
![]() |
" Wrong. The desync kills the leveling, so the only way to progress is being a tank. D3 have a lot of game design issues, but in technical aspect.... damn, it is working. |
![]() |
" this isn't entirely correct. You don't need to be a "tank", however you do need to balance out your defense / effective life and damage. I'll agree that atm a player needs more life/ES than he/she should. But imo it has to do with mob damage (being too high near end-game). Lower the overall damage, just a bit, and we won't see any more "path of life nodes" threads. This is just an opinon. ty |
![]() |
Re: proposed scheme to run exact same simulation on both client and server to solve desync issues once and for all for non-cheating solo players:
" Yes, the game could drop placeholder items until the server fills them in - beautiful. They could even morph from placeholder to the real item graphically as eye-candy. " I like the "monster inertia" idea for multiplayer. People can't react instantaneously, why should mobs? This would be unnecessary in single player mode though. " " Sigh, yes, the second level of cheating. Reverse engineer the client, then run multiple scenarios before choosing which click stream to generate. I really hate people sometimes. One thought for this is that you could *choose* to run the game in this solo-with-no-desync mode. All of your drops are tagged non-tradeable (account bound?) Fine for regular players, and useless for farmers. I'd also like to reiterate my suggestion for separate threads per manifesto post. For me, the signal to noise ratio in this combined thread is 4 to 1, and I'm sure that is also true of the many people who only care about one of the four topics as well. It would keep the discussion more focused. |
![]() |
Regarding desync:
" I understand that this also means that people could cheat, and the results of said cheating would be instant. However, in many game situations, couldn't we still allow the client to do this? In reality, allowing the client to perform calculations isn't necessarily trusting it, it's just allowing it. For example, let's say you've captured a prisoner (in a post-apocalyptic, zombie-infested world, perhaps), he's all handcuffed and shackled, and he's starting to get a real foul odor to him, so you want him to bathe. You would basically have three options:
The thing is, right now PoE never takes the handcuffs off. I understand this is safest, but frankly there's too many prisoners in need of a bath, and it's simply inefficient. I think that, for solo play situations, the game should allow the client to perform operations... but not trust it. The game would still send data to the server on a regular basis, which the server would then perform a quality-control analysis on, thus continually monitoring for cheats and hacks. Right now, the system prevents cheating; this new system would not prevent it, but instead enforce anti-cheat policies, much in the same manner an armed guard would. For other situations -- such as PvP or party vs monster -- all clients should rely on the server for calculations. I understand desync is probably even more of an issue with groups than it is with solo, but in those cases the players are competing against one another (either directly or for loot drops), so you wouldn't just have cheaters, you'd have victims. That adds a whole new level of entanglement that we rightly shouldn't allow. When Stephen Colbert was killed by HYDRA's Project Insight in 2014, the comedy world lost a hero. Since his life model decoy isn't up to the task, please do not mistake my performance as political discussion. I'm just doing what Steve would have wanted. Last edited by ScrotieMcB#2697 on Apr 15, 2013, 10:52:56 AM
|
![]() |
Well its nice that the devs wrote something about the thing that will kill the game slowly, de-sync.
We all know the feeling from FPS Games, a little lag, a ping spike and you explode in a bomb of frustration, but overall the game experience is satisfying. In PoE its the complete opposite if you do not desyncing all the time you are kinda suprised that you can survive in 66 maps as a level80 char without 99% lifenodes, but seconds later you are dead again. Im still playing it from time to time because the item-hunt addiction is still there, but most of the time i simply dont care about that game anymore. Leveling? - impossible Getting instakilled by creeps -15 level to you? - normality Dying because of my own "bad" connection? NOT ONCE No matter how you turn it around the sync solution of PoE is plain bad and will kill it in the longrun. |
![]() |