Okay now it is in fact an exact duplicate of Lapis Commons. I dont get it! Why don’t you guys stick with the essentials-like stuff and build a plugin that makes use of the Lapis Commons toolkit? That’d benefit the community overall, instead of having two projects providing the exact same functionality.
1 Like
@Dyprex I’d like to say that Lapis is a duplicate of Foundation (Foundation was first, even when the purpose changed. You can check that), and we stick with the Essential-like stuff, but in a different way.
Please refer to my post on the Lapis thread, I completely agree with you: [Abandoned] Lapis Commons: Unified toolkit for rapid Sponge plugin development - #38.
1 Like
@DotDash We will definetly do that.
So you mean that Foundation has no use by itself and is only an API? I presume then that the modules will implement any and all functionality, but are being developed by the same team? The only apparent difference is that Lapis isn’t designed to load modules, only to act as a higher-level API, where I presume most of the functionality of the Foundation core is implemented by the Modules you’re also developing for it (and less likely that other users will write their own modules)
@OffLuffy That’s right. You can imagine two layers: the APIs and the plugins that actually do something (Essentials-like stuff). Also, only we (and contributors, of course) develop the modules, because it’s actually a part of Foundation.
So you’re actually going to compete with Lapis Commons? I mean don’t get me wrong competition in general is beneficial, but Lapis Commons seems to be very well-designed for their aimed purpose.
Either way which project started first it’s unnecessary to compete but provide the same functionality at the same time. I can just repeat, a plugin simliar to Essentials would be way more interesting for the Sponge community.
1 Like
@Dyprex We’re currently in an IRC channel, and it seems that the competition will be less than expected. We realize our goals are taking a different path.
I really don’t see the point of this change.
Now, it’s:
- Exactly like Lapis
- Not just a plugin
I just wanted a plugin like Essentials, not an API system… 
Only the Core is like Lapis, somewhat. It won’t be just the core, it’ll be a collection of modules on top of their own API (the core being the API).
@Squawkers13 Our main goal is still to provide exactly the same initial idea. We’ll develop a plugin like that, but Foundation is just a step before that.
Also, me and @Falkreon concluded that Foundation and Lapis are actually very different. Lapis provides functions for plugins like a command framework, scheduling, tasks etc. (more developer-oriented). Foundation won’t provide these things, we’ll include things like teleportation, user-and server management, jails etc. The only overlapping APIs are economy, permissions (which we don’t know IF it will be implemented) and scripting. However, Lapis provides scripting for Lua and Javascript, and we’ll provide scripting for Javascript and Python, so that is just personal preference.
Like i said, a plugin like Essentials is coming in a more modular, flexible and customizable way.
Did you paint that backdrop? It’s quite impressive overall, I’d like that website XD Doesn’t really look like a Sponge plugin sort of page, but it’s nice nonetheless.
That makes sense. Bit of a vague thing for anyone happening across it, but it works. Something like an atom or maybe something like a blueprint may be more obvious. It works well enough, just maybe gives off the wrong vibe XD
1 Like
Could do. I quite like the dark and cool swatch overall though. You can probably pull of a bright or dark warm if you wanted, you seem inclined to design.
I really like that design, keep it up!
1 Like
Jails
You’re able to create a plugin which manages jails, prisoners etc. very quickly.
This can apply to jails, but isn’t limited to other forms like homes, resident regions, stuff like that?