Dave

That's a crazy amount of helpful icons, I'm impressed! Open source is such an amazing thing.

I once considered using this type, but realised it wasn't available in any version below 8.0. Meaning we couldn't use it as part of the framework whilst we support older versions of MySQL. I feel like most situations requiring this field type should really have their data architected differently, but I'll be happily proven wrong.

It’s a front end JavaScript framework: https://vuejs.org/

It’s the same procedural madness, but it’s certainly different

As most of the content on here is old it’s fine for people to respond to older threads.

MNG sent me the source codes and I can confirm these are not MCCodes.

I’m excited to see your framework free submission ?

What’s the mod you’re looking for?

Yeah, that's why I said or something else, just some separation of concerns however that looks. Sounds like McCodes already, you'd struggle to achieve that in an existing framework as they do impose some structure.

One issue with procedural code is duplication of code and poor structure of the modules where in. For instance most the engines we have today combine the business logic and presentation layers which is just gnarly. I think basic MVC (or similar) it's fairly integral to ensure this engine is modern and teaches good practices. Procedural has it's place and it's not for these things personally.

Yeah I don't want to repeat the issues that many of the engines created on these boards before hand. Clever people making bad decisions in the name of owning their creations entirely.

Be the easiest way of getting $50 million in seed funding.

I'm expecting an abusive message from @ColdBlooded once he wakes up haha. I think we collect all popular PHP frameworks, make a poll to select the top 3 or so then go ahead with @Alan's plan of the PoC concept on each framework. I think as you said it should be a small subset of a game engine, something really simple: Authentication Gym Stats UI for training The time window would have to at least be a couple of weeks to allow for people to submit their entries, potentially people might form small teams. Maybe there could even be a prize!

Haha yeah create the Alanguage, create your own crazy syntax whilst you there and I'm sure you'll get mass adoption ASAP in the modern world of programming. Naming is irrelevant unless we intended to market and try profit from the engine, which is certainly not the purpose! Not like those money grabbing fools at MCCodes. That's a new idea, I guess we'll need to decide on which frameworks to trial: Laravel (https://laravel.com/) Lumen (https://lumen.laravel.com/) Symfony (https://symfony.com/) CodeIgniter (https://www.codeigniter.com/) These guys seem to be the more popular ones at the moment. Maybe we can have multiple people choose their favourite framework and build the same concept and vote on the outcomes.

I totally agree, however a fully compliant PSR-7 would require a fair amount of custom, new code, which in turn would have very little support. The beauty of using an existing framework, be it Symfony, Laravel, Zend or something else is that there is support for many fundamentals employed by said framework. Resulting in better all round support for parts of the framework that might not be documented well. Some developers love the idea of creating everything themselves, but in reality in a modern development world that's one of the worst things you can do. I also would say for someone coming into programming for the first time and wanting to learn from the engine (like I did with McCodes) it'd be great for them to have framework experience, providing it's a popular one, to further help their career. People in the software / web development industry are very familiar with the big names. PHP is my go to as it's simple, it's easy and along with the above there's a huge market for PHP developers. There are many other better languages with amazing features, but I don't believe the goal is to create a mammoth proprietary framework / engine in a more obscure language than what this forum, and from my perspective, the PBBG world is used to. DI is an interesting topic, I'm surrounded by it on a day to day basis but this boils down to the engines goals. DI by nature is very much a software concept and it's not entirely needed in simpler applications. It really depends on how we wish to craft the extensibility portions of the framework which in turn depends on how complex we want it. Do we want a download and hack experience (Like McCodes) or a more of a download and extend system. In my opinion the goal of the engine is to: Open Sauce Allow new programmers an entry point into programming to build something they can enjoy Provide a great base to start a game Teach some good programming practices Be simple enough, but well built to appeal to newbies and experienced devs Some modularity so plug and play is possible To answer your tldr; I was just going to call it "Engine" makewebgames/engine is fine and not really a name! I agree some investigation into the framework is important, maybe we don't want to be bound by Laravel's way and use something like Symfony. Don't worry I won't, never trusted that guy ? As mentioned above I'd love to build this in a modern, new, fun language. But fundamentally it's a nostalgia project to try achieve the goals above. These are all just my opinions on working with proprietary software with it's own implementation of basically everything in software engineering. Magento is a beast.

I actually set this up yesterday ironically: https://github.com/makewebgames Yup, we'd use anything that Laravel provides out the box, like the auth. We'd need to determine if we wanted to use things like the service container, or if we want to use facades only. The extensibility side of the project is the complex part, as with more extensibility you introduce more abstraction and complexity. It'd need to be a nice balance between being a nice powerful framework whilst being easy to learn and easy to plug modules into.

I agree, the framework of the engine will be the first priority. In an ideal scenario we'll have pluggable feature sets. So we can create meta packages of gangster, fantasy, sci-fi etc features. The core would contain everything typically shared by all genres: Authentication Communications Notifications / Events Donations / Payments Stats User Attributes (money, etc) User Preferences Admin Framework Theming Probably some things I missed in the above.

The front-end framework is up for discussion, Laravel ships with good Vue support so it seemed like a good decision. Truth be told I've not written much Vue either, but it's got a pretty easy learning curve I believe.

Oh damn, do you live in the forest of something? My home internet is insane:

It's been a long while since I built or touched any of the popular game scripts that are around today. However since resurrecting the forum the nostalgia has become very real. I've been toying with the idea of creating an open source community engine based of modern frameworks and using modern technologies. My thoughts right now are: PHP 7.x Laravel MySQL Vue.js I'm looking for suggestions on the technology stack (should we use React? for instance) and for anyone who wants to contribute into the engine. If the engine goes well I'll certainly skin and launch a game with it.

If I get a chance to grab the old URL I shall do.

I'm rebellious. I didn't even realise that it auto selected somewhere so far away. I imagine the ISP only has that server setup, as it tries to select the closest one on your ISPs lines I think.

I think you'd be the only user I'd use that on.

Has anyone else watched Disenchantment from the creator of the Simpsons? I really liked the little devil cat thing, overall found it quite funny and nicely different from The Simpsons / Futurama. https://en.wikipedia.org/wiki/Disenchantment_(TV_series)

Safe to say my internet at work is nothing special. I get 300mbps at home, so I'll post that later.