a_bertrand

BTW I would personally use the translation of AP into something else instead of changing the stat directly otherwise modules which relies on the AP stat will break.

yes it's good idea, even if maybe it's not smart to have very large tables.

Username selection, or other using the smart selection feature of the engine should be already partially covered. However the table editor and such don't have yet a paging and should integrate something (as well as a filter / search). It wasn't my priority, but we could think about it if you think it's already the moment for such feature.

That's the whole goal of the token part and it's done by the security_token module. And as illusions said, you can guess the IDs, or whatever from the URL but: 1) You can't mess with them (the token is URL dependent and session dependent, so even if you login a second time, the token will be different for the same exact operation). Messing with the URL kick you out. 2) Most modules do check if you have actually the right to do this operation or not (or at least I hope they do it). For example the forums check if you have the right to view this thread or not. So overall, even if you guess how things works and you understand those numbers links to id inside the DB (which honestly is not hard to guess), you would not go very far.

I would would use the engine features instead of printing out the links and such. Also you are quiet certainly missing a menu, and maybe a config.xml file ;) Why not download the free version of the engine and try it yourself?

Modules are examples of what can be done and how to do it, as well as provide a base to build upon to (for example you may expand one of the module any way you like it) as well as provide some functionality to those which are less skilled.

You may check this: http://makewebgames.io/showthread.php/42433-Free-V1-V2-MOD-Horse-Racing-ported-to-NWE It's a port of a McCode module to NWE... Not only port but nearly a re-write. If that's not enough you need to say exactly what are your problems and then we can dig into it.

I know, simply put not all is yet perfect in NWE ;)

So you are in the wrong section, you should post in the McCodes area ;) But as I'm a "really nice guy" too, I will move your thread for you.

A license of what? Of a dirty socket? Sure give me your postal address and I will send it. Seriously you should be a bit more explicit. Also why someone should sell a license of McCodes or NWE fo 40$ ? Seems really low when both are around 100$

Like a copy of what you send you mean? I will look into this.

Well that's doable if you really want it, but then poor pants! And poor wife which need to wash them !

Would need lot of art, and would not be really generic. Doesn't make sense that I do the art for something like that.

I'm lost gmoore, I don't understand what you say. You say that the version of inventory and ajax_auto_refresh are older than what is offered by the 1.1.5?

Why should we use your service instead of posting directly to youtube, vimeo and others?

Depends about the quantity, you could always print all and show only the best one first and only show the others in case they ask if you have anything else. Or just show the best one saying those are some of your best.

Staff page: will do it soon. For the donator, could be handled by adding a stat and setting it up. I will check. Voting: it pretty much depends on the voting site, so I hardly see how a generic module could cope with many different API.

Orsino: no bugs it's on purpose it's the usual text workers in casino say. You can anyhow change all the texts from the admin panel. gmoore: it seems emails are mainly filtered out. If you need something send me an email to [email protected]

Thanks ;) It took me actually nearly more time to draw the roulette than coding it.

This release is a mix release, between small and not so small bug fixes, to loads of small improvements. Many of the fixes are already available as module updates, anyhow we shall summary the changes since 1.1.4: - Fixed all the config.xml files to comply to the XSS - Added a admin_put_in_jail - Fixed admin_side_panel to let you edit the core configuration keys - Fixed some combat issues - Fixed some chat issues - Added crime module - Fixed explore module - Fixed forums module - Improved the inventory (now can collapse object types) - Fixed locations - Fixed mines - Added mix module - Fixed exploit in the npc_discussion - Added player_barter - Fixed register - Added roulette module - Fixed russian_roulette - Changed the hook of the view_player - Added stop timer in the AJAX lib - Improved the DB library - Improved the template library

A new European roulette is available for free to all full game owners. The game currently is relatively simple, you can bet what you want on any number and if you get it right you get 30x the amount bet. The full roulette would have additional options which are currently not implemented. However there is a few good things: - Have art and is animated - Works in AJAX (without page reload) - Art is copyrighted by me (made myself) so don't worry about copyright issues ;) [ATTACH]848[/ATTACH]

Ok I managed to do yet even more, basically the library doesn't load the column names till you try to use them either as array key or as object property. So until you use them you will have very little speed impact (nearly none). So a module which uses them will use them otherwise it will remains more or less like before. Code compatibility is saved, as well as speed yet offers different ways to access the data. This will be included in the 1.1.5 which shall be available in the coming days.

Happy you managed ;) And yes the framework offers loads of small goodies.

Yes I allows it ;) And really nice tool congratulations Dj! Added it to the wiki page here: http://www.nw-engine.com/wiki/index.php/Main_Page#Tools

Maybe I found a compromise which would please all (me too): $result->fields will by default not query the column names till you access them, at that point the column names will be retrieved and populated, which means if you don't access via column names you should have very little impact in performances and yet if a module requires it it will retrieve the column names and therefore have the compatibility safe. What do you think? Would that be acceptable? I will make some tests tomorrow if I have time (tomorrow being a nasty day for me).