Cheech

You're going to host weekly contests for 2 weeks until you get bored and forget to do it, then say that there will be one next week, but then there won't, and this will all fade away; I know how you people work.

Yeah, the fancy overlays add some nice colour, but I'd argue that all of the real value is simply in the tile placement. These maps would still be just as great without the overlays.

I've comprised a list of maps that I feel should be inspiring towards making yours better: http://www.freemmorpgmaker.com/thread-85605.html

Hey folks, I was asked in another thread to show someone what I consider a good map to look like. Well, I figured I'd start a thread of inspiration, since the majority of you suffer from making bad maps. I don't mean this as an insult; I was never that great of a mapper either, but maybe if I can show you some of my favourite maps, it might help you to improve your games. Now, most (if not all) of these maps will be from RPG Maker, but the same principals stand. The points that I want to stress are as follows: * **Nature is not symmetrical**, it is **not comprised of squares**; it is messy. * Towns are also not symmetrical by nature. Castles? Sometimes, but **most real castles are not symmetrical eithe**r. * Town builders **do not leave wide open areas** between buildings; maximize your space. * Indoor maps do not need to take up the whole screen. **Houses are small** on the outside; are your villagers Time Lords? The best mapper that I knew's username was Kiriashi; he disappeared a few years ago, sadly, but a lot of these maps were his.                         Hopefully these maps will help to inspire you!

Actually, I think it's worse in your outdoor maps; indoor maps are already unnatural by simply being indoors.

Your maps are awfully unnatural; too square-ish and symmetrical.

So, this thread is just to gather people's thoughts and criticism for my MVC framework; I'll create a new thread with a release announcement when the time comes.  **Blackbeard** is an _opinionated_ **MVC** framework built on top of Node.js, using the most current and future versions of the ES language spec. What does this mean? Well, it means that you can take advantage of some of the upcoming and recent arrivals in the JavaScript language: * Classes * Annotations * Lambda expressions * Async/Await * Modules So, using all of these great new language features, what then does it mean for the framework to be "opinionated"? Well, it means that we make it really easy to correctly implement an MVC pattern by giving you an API that does most of the work for you. The framework does also assume a few things (and throws appropriate errors if those assumptions fail). No worries, though, setup is really convenient and takes care of some of the boilerplating for you. Well, enough with the long-winded boring stuff; let's get to the fun! Here's an example of a very simple controller: ``` import { Controller, View, Router } from 'blackbeard'; const { MapRoute, GET } = Router; @Controller class MainController { @MapRoute('/', GET) async index () { return new View('index'); } } ``` If you're familiar with .NET MVC or Spring, you can see that Blackbeard will already be familiar to you. It was built to be simple and familiar, yet fast and powerful. Here's another example of a more complex controller: ``` import Forum from '../models/forum'; import { Cache, Controller, DataString, Requirements, Router, Session, View } from 'blackbeard'; const { MapRoute, GET, POST } = Router; const { isAuthenticated } = Session; @Controller @MapRoute('/forums') class ForumController { @Cache(60) @MapRoute('/', GET) async index () { const forums = await Forum.findAll(); return new View('index', forums); } @MapRoute('/{id}', GET) async forum (id) { const forum = await Forum.findById(Number(id)); if (forum) { return new View('forum', forum); } else { return new Error(404); } } @MapRoute('/{id}/delete', POST) @Requirements(isAuthenticated) async delete (id, request) { const data = JSON.parse(request.body.toString()); // do stuff with posted data await Forum.destroy({ where: { id: Number(id) } }); return new DataString('application/json', JSON.stringify({ success: true }); } } ``` As you can see, due to the nature of the API, the annotations make it very simple to define your controllers and routes. My questions for you all are, what sort of features would you love for an MVC framework to have? Do you have any concerns about the API? Would you use this upon the beta release? Thanks!

Let me know if you got the money.

All of them are terrible tier.