It looks like you're new here. If you want to get involved, click one of these buttons!
Originally posted by Loktofeit Originally posted by l2avism With so many indies buying these "engines" to make games they won't finish there is obviously more money being made selling these engines than making indy games.
Because it's easier for a someone to convince himself the problem was a limitation of the engine rather than a limitation of his ability. As we've seen from other threads here, a good number of MMO gamers think they can actually create a decent MMO, so it's easy to sell them engine after engine.
Sometimes the reason they relied too much on finding the "right" engine that could do all of the heavy lifting for them is precisely that they lacked the necessary ability to do things for themselves.
There's nothing wrong with using a game engine that will do a lot of the stuff that you need and do it pretty well, while leaving you the flexibility to do yourself the stuff that you need and the engine doesn't have built in. But if you need the game engine to do everything hard for you because you can't do anything hard yourself, that's not going to end well.
Originally posted by William12 Cryengine is garbage if archeage uses that i would stay away from the game it is NOT ment for MMOs developers keep using these single player or FPS game engines thinking they can make it work but they cannot and the same goes for the hero engine. Best MMO engine ? Wait for it Forgelight from SOE http://en.wikipedia.org/wiki/Forgelight_Engine Just play planetside 2 once no lag nothing the engine is perfect for massive open world MMOs with hundreds of people on the same screen. Go try and get 400 people in the same area using hero or cryengine.
By the comments here, their is no way you have experience at all with game engines, Cry Engine is fine Star Citizen is using it, State of Decay has used it, I use it almost daily, it crashes just as much as most of the others when using, people need to learn on what they can and can't do . Some people think you can do anything and it won't crash, well use it correct and it won't crash as much.
All engines crash when making a game, But Unity is one of the better ones and its making head way more and more every day, it also is damn easy to use.. Unreal crashes as much if not more then Cry Engine.
Hero for a small company is the best route by far, it is easier to use, or use Unity Pro 4.2 or what ever the new one is, I have 4.2 .
Also the one form SOE, I have nothing to say besides LOL...
Originally posted by Quizzical Originally posted by Loktofeit Originally posted by l2avism With so many indies buying these "engines" to make games they won't finish there is obviously more money being made selling these engines than making indy games.
TLDR: Not always the case though.
If you are after a specific design you could spend years and years making the engine do exactly what you want in scalability or you can find the somewhat right engine to do the job somewhat and rather poorly at best. It is a matter of when you find the right engine and when you have researched the right engine and UNDERSTAND how it works that you can start processing your design. Creating a SP game is easy. It is when the networking and database accessing starts to make things tough and having an enterprise level engine with enterprise level database become critical. It is more critical for security that 99% of the game mechanics are server side and the client is nothing more than a dumb terminal to look at the server persistent. So many of these guys go off making a game and put way way to much functionality into the client. They make the server side of it just basically a glue code to show others in the AOI. If you ever intend to make something that will allow more than a few concurrent connections then you need a engine that can do the fucking job!
As for the end product you still need to do the work and understand the engine and its limitation. It is up to you and the team to make that part happen. Yee, yes the game is YOU and YOUR team and their skills. The engine can’t do that for you and never will. Again, making a complex product like a MMORPG either requires a good team to build the infrastructure or an existing proven engine that can do the job for you.
I got off my lazy ass recently ( like a month ago) and started programming again (took 5 YEARS off programming which is way way to much time fucking around with these engines and not enough time writing code) I was going to just sit around and mess with the engine but I got this itch again to build KoW and I am going to continue with or without any support. BWT is a engine that is just amazingly phenomenal in its functionality and I don’t have to touch a fucking line of code to make it work on a client/server relationship. It follows the requirements of KoW as I gave it to ...
1). – be capable of handling a seamless world up to 100 Kilometers square.
2.) – Have a capability of 6 degrees of freedom without pigeonholing players into any forced direction. (The world can lap onto itself if I want it to.)
2). – be capable of distributing the processes across an infrastructure automatically without intervention in a distributed controlled network.
3). – be capable of object linking across a wide spectrum or classes.
The internals are handled for me so I can concentrate on my design and functionality of my design instead of spending thousands of hours trying to make distributed computing work as intended now.
My designer and I sat down and discussed how we are going to build it. We took the first basic building block and designed it with the follow requirements.
1 - All harvestable items in the game world will be static. They will hold a certain amount of product. We could have made it random location but decided not to. The location is fixed because we are going to use a base that will stay once the node is harvested out.
2. – Each harvestable node will have a required tool and skill level.
3. – The number of different node of one type can be expandable up to any limit. We decided to limit them anyway but 255 node types of any category makes way more then we will ever use.
4. – If a player is harvesting a node they can not harvest another.
5. – Any number of players can harvest the node. I set this at 10 by default it could grow so 255 players can try to harvest a node but then it becomes server time issue. Unless I put this on its own cell. (server) Really not a limitation but for a single server it can be a bit hard on game ticks.
6. – If the player moves they will interrupt the processes. (needs fixed atm so interruption is instant. BUG)
7. – Once the node is harvested out it will vanish and will respawn on a timer depending on level and class of node.
8. – The harvest time is fixed for each level But is reduced by a percentage for each skill level of the player and which level of tool they have but it is fixed to go no less than one second.
So we had a design that would cover all harvestable nodes in the world BUT we decided to make different types because a tree we want the stump to be harvestable and when the stump is dug out the tree will NEVER respawn. Clear the land of trees in areas where it is allowed. Every tree in the world is harvestable.
I sat down and examined the requirements and built a class for ore nodes based on this information. He created a spreadsheet of 10 different ores with different times, count, level requirements and so on. I then made a database entry of the class based on the information I had. AND finally started writing code.
I made a class called pickaxe that attaches to the player hand. (no model atm)
Since I never want the player able to cheat I made 5 lines of code in the existing client. One to point to my classes this activates when the player clicks on the node and uses his pickaxe.
As the code progressed, I found that at some point the player that harvested out the node never cleared the other players so I made a internal array of players on the node. I found that a player could effectively disable the node by quickly exiting the game and relogging so I made a conditional check when it was full that all IDs were checked if valid against the existing players in the cell.
After all the checking was done and the timer ran out, I put the ore type into the players inventory and calculated the experience. If they leveled past the next level requirement, I leveled them up.
So the end result was under 100 lines of code that covered every single ore node in the game world. It took about 15 hours to write and debug.
This is all server side by the way nothing graphical going on as the video here will show. I am now in process of making a new class that will do something else and I am not at liberty to discuss that since it makes KoW very unique.