Snapshot? Can GGG even fix the mistake?
" I think the fix would be extremely complicated. I actually think Jieran and I can agree on that. Mark's post pasted earlier indicates it could be fixed but it would be harsh to summoners. I don't necessarily agree as I'm currently getting along fine as a summoner who hasn't snapshotted once but for people who based their builds on snapshotting it would certainly suck. Maybe they should do a scream test. Take snapshotting out for next 4-month league. :) POE Serenity Prayer: GGG, grant me the serenity to accept the RNG I cannot change,
the courage to challenge any unbalanced content, and the wisdom to avoid the forums. Mad: "Oh, it's simple and if you insist... I just think you're a dick. That's all." QFT: 4TRY4C&4NO | |
|
Also, multiple developers on one or more projects in no way restricts OOP so that it has to "not interact with anything else". In fact, good design and up-front planning of interfaces allows you to mock out other modules you need to work with when testing your code, and let the part of your application that hooks everything together handle the 'real' instances of what you need to talk to.
In other words, if I'm writing Module A, and someone else is writing Module B, but that guy also has other projects to do, it doesn't mean I can't do anything that interacts with Module B and I have to duplicate anything I need in my own module. Both developers would design and document interfaces, such that Module A inherits from Interface A, and makes calls to Interface B, and Module B inherits from Interface B. Module A doesn't know anything about the specifics of Module B, and unless an interface signature changes, doesn't get *directly* impacted by internal changes. When I test Module A, I write mock code that inherits from Interface B, that my module talks to. Then, when everything is put together, the application glues Modules A and B together through their respective interfaces. | |
" Yeah, I got a bit sidetracked with all that "Single threaded isn't single threaded..." stuff. To me using the phrase "hard-coded" can refer to both the type of input you're referring to but also behavior. I agree it's a bit of a misnomer here because we're talking about something that isn't so simple as a single method that always returns "foo" but when a behavior is hard-coded it cannot be changed without access to the source. In some languages even function behavior can be dynamically loaded from input streams instead of being hard-coded. Anyway, that's really not the point. One would think the fix would be fairly simple by doing a gear/gem check after zoning and removing any skills/buffs that are no longer present. They already drop things like AA when changing zones. If you unequip an item while in a zone which contains, say, a raise zombie gem, your zombies raised with that gem croak. If you unequip an aura gem while in town you lose the aura. It seems all the necessary functions exist but just aren't applied to certain skills. If that's the case, then most of this conversation has been moot and the real issue isn't can they do it but instead is are they willing to piss of a bunch of players by removing it? POE Serenity Prayer: GGG, grant me the serenity to accept the RNG I cannot change, the courage to challenge any unbalanced content, and the wisdom to avoid the forums. Mad: "Oh, it's simple and if you insist... I just think you're a dick. That's all." QFT: 4TRY4C&4NO Last edited by Phaeded on Apr 21, 2014, 7:20:36 PM
| |
" One might think that, but one would be making large sweeping assumptions about the design of their systems and the state of their codebase. After having worked on or written a few systems with large, long-lived codebases, one would instead assume that there's a reason -- whether or not it's rooted in what would be considered improper separation of concerns or some other flaw in design -- that it's not trivial to change the behavior in question. If one was working on such a codebase with the intention of changing the behavior, one would accept this with a heavy sigh while making incremental improvements that would eventually allow the change in behavior to be trivially made. This would not be a task one could complete in a day. http://www.twitch.tv/exhortatory
|
|
|
so everyone goes snapshot and there is no problem.
| |
|
rather than fix it, is it possible to make snapshot a legit thing and make it a mechanic that everyone can benefit form it.
you know OP items + OP skill = lots of "poe is dying" posts Last edited by Tom1989 on Apr 23, 2014, 9:54:09 AM
| |
|
yea lets make it legit so we can all go to fight ubers and cast all of our auras then used 80 regrets to re spec all those auras nodes into es nodes cuz that makes sense
| |
" The day that gearswapping becomes a main method to playing the game is the day I'm out. Snapshotting is about as exploitative of a game engine as a method gets. If it is difficult for them to fix, I'll be a bit patient... But legitimizing it will drive me off, and I have always loved the game, despite the frustrations it brings through loot, desync, and bugs. | |
" yea i know. i want this problem to be solved too. but snapshot is there like since closed beta? It seems that it cannot be fixed. sadly, gearswapping is a main method to playing the game. hey, look at those summoner and RF char. and i bet that there are more. to be clear, i dun hv a shav and my main char cant benefit from snapshot. Last edited by Tom1989 on Apr 23, 2014, 10:54:40 AM
|
