Did they actually fix that game? I loved it, but oh lord what a buggy bag of shit. I logged in just for shits and giggles about a month before they shut it down and got three sb.exe errors inside of 2 hours. I would have never stopped playing it had it been even remotely stable, some of the siege moments I had on my fury and confessor stand out as some of the best fun I have had in an MMORG.
Note : I played EVE super casually for like 2 months so I have no vested interest.
I'll add it's not going to ship complete they're going to ship as soon as they can and we the beta testers and early players get to help fill out the world.
So SOE is allowed to do it, but other companies are roasted alive for doing it. Funny how nostalgia is seemingly overriding the usual cynicism, criticism and anxiety that every other MMO is hit with ;P
/shrug
What's the difference? (Genuine question.) Based on my limited knowledge of each, it seems like the only real difference is that Project Spark lets you create a wider variety of things and it allows you do so while in game. My real problem with this kind of player-created content isn't that Dungeon Maker wasn't good enough, it's that it destroys everything a real sandbox is suppose to be about.
It's option 2, mostly. I don't know where you got this fixation that player created content has to be instanced. Smedley's examples of world-changing by players were mostly in-world (e.g. burning down a forest). Project Spark-like tools are much better for in-world creation than making seperate planes. I'm not saying there won't be some instanced content in EQN (because clearly there will be) and I'm not saying their won't be some player created content that is instanced (because there might be) but all signs point to most content (whether dev or player-created) being in-world.
The difference between 1 and 2 isn't instance and non-instance. The difference is whether the changes in the world come about organically through playing the game or whether they are made by a developer (paid or player) who decides "oh, a building would look nice there, I'll just click this building button and place it there."
Eh no. I'm pretty sure of about 80% of what we're going to get (seemless world, EVElike PvP, original continents, player created content, storybricks AI mobs, storybricks quests) so I'm mostly interested in that 20% I know I don't know and have been unable to guess at based on the hints, tweets and interviews: things like the "spellweaving" quote, whether it will have OT/DT, whether combat is button mashing or resource management, etc. I will be disappointed if there is no OT/DT and combat is button mashing like Rift.
Not sure how else to explain this; I'll try using your example. If you are running through the Karanas and decide you want to put a keep down, then you should have to have the skill to build it along with the necessary resources and then actually build it. Alternatively, you could pay an NPC or another player who has the skill and resources to do it for you.
I'm guessing he means more, 1)do you go in to an overhead view and slide a ghost representation of what you are going to build around the map until you find a place, click once and poof it's there, or 2)do you buy the plot it's going In then either learn the carpenter profession and build it bit by bit over time like you did in vanguard or pay someone else to do the building.
I get what you meant but there's other stuff going on in the background beyond just skilling up in carpentry. A player or dev has to design the keep elements (moat, bridge, main gate, chapel, etc) that's where the project spark/player studio stuff comes into play. We've been talking about two completely different things.
That was my original supposition, but the deleted bit in the last mini-video release convinced me that they expect the players to help them build the world and since it is mostly non-instanced that means building during beta or live.
He obviously means his cock. I think we are going to have to tug him off to get the infoz on the 2nd. Someone needs to take one for the team.