Herp Derp.
Fixed.
Well, according to our wonderful GitHub Milestones:
Version 1.0 is due out by February 27, 2015. This will be “the API release” with our goals being:
All of these working.
◦Economy API
◦Core API
◦Module loading
◦Ban API
◦Server Management API
◦Teleportation API
◦Formatting API
– Also, according to GH, this is 33% complete. –
Version 1.1 (“the Core release”) is due before April 6, 2015. However, this is by no means final and may change at a moment’s notice. We aren’t sure of all of the goals yet, but we defiantly need:
*The Core - Essential command and things like that.
*API: World Manipulation (like tools for making a WorldEdit like plugin, if you so desire) and any leftover bugs we might miss in 1.0 or extra patches/minor releases after that.
– This is a HUGE project and we’re still going full steam ahead, although we had the big inactivity period. Now, myself, along with @Exstar and now @WetSponge, we can pull off the most essential plugin in Sponge, with the core being possibly released soon after a Forge implementation of Sponge (i.e. the usable/runnable server) is released.
Consider that an official press release.
~ @ButterDev, for the FoundationDriven team.
http://twitter.com/foundationdev

A brief history of Foundation…
I created a little history of Foundation. You can really see how hard we’ve been working! This photo is taken from the GitHub charts, which is public on the FoundationDriven/Foundation repo. I added a few notes of my own for relevance.

Even more confusion cleanup!
You may have heard that Foundation will have modules. And an API. So, naturally, some people will get confused. It’s okay! I’m here to clean it up.
-
Module != Plugin using API
A module is an add-on to the core of Foundation. Modules cannot function without the Foundation core. A plugin using the API is a completely independent Sponge plugin that uses the Foundation API. -
What defines a module?
Modules are defined by the@Moduleannotation. For example:@Module(name=“Awesome Swaggy Module”, id=“foo”, minFoundationVersion=“3.6.1”, maxFoundationVersion=“4.8.4”)
public class SwagModuleMain {
…
}
Q: So, I’m ready to make a module?
A: No, we need a core before modules. We don’t have a core.
Q: Can I work on MySwaggyPlugin in the meantime? It references your API…
A: No, the API is still in development, too. v1.0 is expected by late February 2015.
That’s all from me,
@ButterDev out.
Core Rewrite! - 12/15/14
The wonderful manager of FoundationDriven, @Exstar, has decided that Foundation’s core was too broken to even attempt to fix and I wholeheartedly agree. Although the core wasn’t even near functional, over 200 lines of code have been deleted. He has said to expect some big commits to the [GitHub repo][1], so I’m excited to see what comes from this. Also, keep in mind that the API is currently a priority.
API Status Update - 12/15/14
ECONOMY API: In development by @Exstar
BAN API: In development by @ButterDev
TELEPORT API: In development by @WetSponge
MODULE LOADER API: Planned, assigned to @Exstar
MODULE LOADER (Not the API): Planned, assigned to @Exstar
WORLD MANIPULATION API: Planned (not due until v1.1) Planned.
Your friend from FoundationDriven,
@ButterDev
[1]: https://github.com/FoundationDriven/Foundation “GitHub repo”
Got implementations? - Status update 16/12/14
Stuff has happened.
Misc
-
Javadocs are now up on the website
Fully Implemented APIs -
Teleportation API
-
Formatting API (Explanation)
-
Economy API
In-Progress APIs
- Ban API - @ButterDev
- Module Loading - @Exstar
- Module Loading API (?) - @Exstar
Low priority APIs
- World manipulation API
Thanks,
Oscar.
On target!
@ButterDev Awesome, but the module loading system takes a lot of time to design and implement. However, it should be finished this week.
Ban API update - 12/16/14
Version 1.0, according to GitHub is complete except for one pesky little thing, that being the Ban API. I am coding like crazy and I aim to have this complete by 12/20/14
Ready your IDEs. Foundation’s API is near.
Nice to see you guys are back on track 
@DotDash Yeah… 
Also, I just pushed a commit: “Ban package (almost final)”
I do not like this! It is not even thread-safe! And the formatting is very not conventional!
@Nack_Seerosja could you please elaborate? If I can make my code better I would like to do so.
public class @Nack_Seerosja {
public boolean isGrammarNazi {
return true;
}
It’s an expression. And I know that, I studied the Holocaust. Now, you need some thicker skin on the internet.
That document is 17 years old…
@Soren Thank you!
I’m getting tired of you, @Nack_Seerosja.
User @Nack_Seerosja = new SpongePowered().getUser(@Nack_Seerosja)
@Nack_Seerosja.getAccount().deleteAllInstances();
Because it’s still being updated. See Java SE 8.
Because this
http://www.oracle.com/technetwork/java/javase/documentation/codeconvtoc-136057.html
Is labeled in big red letters with this

note the “the information itself may no longer be valid” part