a_bertrand

Quests & story and exploration.... those are the things I'm after. And they are not in your poll. As well as logic / puzzle.

either modify the file modules/premium/content.php or use the sentence editor to change some of the existing texts without changing the code.

It wasn't bad but neither incredible... just a medium Dr. Who in my opinion.

For your "4. Needs (More than just HP/AP; hunger, energy, etc.)" you know that you can add as many stats as you want without changing the code?

If it's in the npc_warrior table, then reload_energy is what the NPC will gain at each "round". The energy is then used to know if at that round the NPC (or yourself) can attack and what kind of attack can be done. item_drops are basically like that: item_id/percentage_of_chance,item_id/percentage_of_chance,... so you split all the possible item drops by a coma (,) and each item have it's own probability to drop. NWE is certainly different from McCodes, as it was designed as more flexible, which means offers more customizations options than McCodes (without changing the code that's it). Stats for examples are defined in the DB not inside the code.

1) It's a set of pre-made code which should help your in some tasks. It could contain for example ways to load and save data from a database or easier way to present your data. 2) A good framework should help you write cleaner code and concentrate on the business logic (the logic of your application) while removing some of the work from your shoulders. 3) You should use one if you have the need for it. 4) Depends on the language you want to use and what you want to do as application. Just like that it's a bit hard to answer you. I guess you want to use PHP, then watch for the big framework out there like Zend, CodeIgniter, CakePHP, Symfony or others. Check out for example http://www.phpframeworks.com/ to see which one fit your needs best. Anyhow, as always, you should either choose something after you know what you want to do and evaluate which product fit better your needs, or if you will work for a company you will have to work with what they already use there (usually you can't join some team and impose your own way to code).

Make sure you log out / log in again after you change the stat_types table, as those info are cached in the session for performance reasons.

What does a step by step means for you? Usually a step by step means for me that I'm guided to some procedure to do something. Here you want info about the existing stats of your game... not really a step by step for me so I'm lost. Just ask here in the forums exactly what you want / don't understand and I shall try to help you. Dexterity is used during combats and maybe while you try to wear some item. Reload? Where did you saw it? item_drop for the NPC warriors let you define what kind of items a player could gain from a combat.

It could very well be a problem with your hosting, would it be possible for you to try to install it on your own PC after installing XAMPP or WAMPP? As anyhow that would be the best solution for the development: develop locally and then once you know it works upload it to your server.

In the table user_stat_types you need to set some value to the restore_rate of your new stat (nerve). AP have a value of 0.5 which means it restores 1/2 an AP per minute. It's the module restore_stats and more specifically the auto_pre_content.php file of it which does the start restore, you may check the code to see how it works.

Well... this creates a special server, so you can't run that simply via Apache as you usually run your PHP files. That need to be run on the server side ( http://code.google.com/p/phpwebsocket/source/browse/trunk/%20phpwebsocket/server.php ) and started with the PHP Cli environement. Sure thing, then it may work, but usually a shared host will not allow you to run your own processes. You will have more luck searching for a node.js hosting or an ASP.NET hosting and then implement the web sockets there. This was the reason why I said PHP was not the best choice, because basically as Apache module (or any other usual web hosting solution) PHP doesn't let you server web sockets.

But forget websockets and PHP together.... PHP is not the right choice here.

No wsirc doesn't use flash ;) WSIRC is pure Javascript both as client and as server. It uses socket.io but without using the flash option (anyhow it's not anymore useful with IE 11 running on Windows 7 or above).

Definitively use node.js with socket.io or signalr with .net Anyhow the best bet here is websockets. IE 10+, Firefox or Chrome will all work fine with it.

Lucifer: could you stop to wake up old threads? Threads older than 1 month are usually useless to wake up.

Try the free version of NWE: http://www.nw-engine.com

C is not OOP, C++ is.

Well, another 5 years of life if that's what you think, it's still far from being dead in term of software life. Plus you know that many still use CVS? ;) Anyhow I will definitively agree that GIT is slowly but surely growing.

http://www.ohloh.net/repositories/compare

well... as said I'm not sure about your info. GIT does offer some advantages as well as quite some drawbacks as well.

*Cough*, *cough*, SVN dying? Way not sure about that. However GIT, Mercurial, SVN, or others would be the way to go for sure.

Photoshop is certainly ahead of anything else, yet GIMP is not bad, and I would suggest GIMP if you want a free alternative. Paint.Net is good, but far from being as powerful. Maybe easier to use.

Well I tried again and don't have any issues, can you give me a step by step way to reproduce it?

If you hash them (MD5, SHA1, SHA256 or whatever) think that you cannot recover them (yes yes, rainbow tables and others can), so it is basically useless as well if it is to store password for services. If it is for your own site then sure use that.

TEXT doesn't have limit (or nearly) on the size of the field. While VARCHAR you need to define the size of it before, and you cannot store more than that till you increase the size. There is also a limit of how big you can store in there. For a password, I doubt you go anyhow to anything longer than 32 char... so Varchar would be the way to go. Yet... Security wise, I'm far from being sure I would do a DB with all my passwords ;)