I love this. I do have one concern. If you have a protected land using a Bukkit plugin, and then used a forge mod on that protected build, will it destroy? If Sponge offers a thing where you can have plugins using mods or plugins and mods don’t conflict and a protected land using a Sponge plugins won’t be destroyed by a modded object like TNT. I want to see you use that to allow Bukkit plugins to interact with forge just like Sponge could. Is that in any way all possible?
So its not out yet? And any bukkit plugins work?
Some simple things work in essentials, like homes, warps, and spawn. If you want something more complex you will have to wait a while until it is finished.
Conflicts like this can’t be avoided even between plugins on the same platform. Similarly, we can’t really take steps to prevent them if they do pop up.
Who knows. Probably the plugin translates Bukkit events to Sponge events and since Sponge has plans to allow its plugins to interact with modded blocks. Or it could just add Bukkit events to Sponge and runs bukkit plugins off of that, conflicts as you stated can not be prevented. I do not know the code that makes up Pore and Bukkit and what Sponge itself can allow but I do understand a few things. Thanks for the reply.
It’s been a while since the last official status update, so I thought I’d give one now while I have a few free minutes. Development has essentially halted since the summer, since (as I’ve stated before) the team basically consists of two people and we’ve both had other commitments and projects which have taken priority. In addition to this, the project, at least for me, has become fairly stressful to work on due to all the breaking API changes taking place. However, the Sponge team has stated it intends to get all breaking changes out of the way in time for 3.0, and so I imagine Pore development will pick back up in 2016 once this happens.
The main point of this update is to clarify that Pore isn’t dead. I won’t deny that it’s on a hiatus, but we’re going to finish this thing one way or another. Anyhow, merry Christmas, happy holidays, etc. 
11 Likes
Awesome Idea!!!
L-O-V-E IT
Does This Work With WG(World Gaurd)
Currently no plugins are officially confirmed to be working, but WorldGuard has a native Sponge version in the works (or maybe complete at this point, I’m not entirely sure).
Thank You 
Worldguard has not been ported to sponge at all at this point in time.
Feel free to check out foxguard as a replacement.
Ahem…
Find me a working build.
I never said the port wasn’t started.
Wizjany has been working on it for quite some time.
I just said it hasn’t been ported yet.
I Already Checked It Out, i Noted It Is Yours 
1 Like
You said it hadn’t been ported at all. I took that to mean you weren’t aware of a port having been started. My mistake.
It’s cool. Have a hug.
1 Like
This project is still active?
1 Like
I have an error,
[Sponge]: Could not pass FMLServerAboutToStartEvent to Plugin{id=pore, name=Pore, version=unknown}
at blue.lapis.pore.Pore.onAboutToStart(Pore.java:114) ~[Pore.class:1.0.0-SNAPSHOT-git(master-a5ab5f1)-jnks277]
at blue.lapis.pore.launch.PoreBootstrap.onAboutToStart(PoreBootstrap.java:79) ~[PoreBootstrap.class:1.0.0-SNAPSHOT-git(master-a5ab5f1)-jnks277]
at org.spongepowered.common.event.listener.GameAboutToStartServerEventListener_PoreBootstrap_onAboutToStart8.handle(Unknown Source) ~[?:?]
at org.spongepowered.common.event.RegisteredListener.handle(RegisteredListener.java:86) ~[RegisteredListener.class:1.8-1577-3.1.0-BETA-1025]
at org.spongepowered.mod.event.SpongeModEventManager.post(SpongeModEventManager.java:233) [SpongeModEventManager.class:1.8-1577-3.1.0-BETA-1025]
at org.spongepowered.mod.event.SpongeModEventManager.post(SpongeModEventManager.java:277) [SpongeModEventManager.class:1.8-1577-3.1.0-BETA-1025]
at org.spongepowered.mod.SpongeMod.onStateEvent(SpongeMod.java:167) [SpongeMod.class:1.8-1577-3.1.0-BETA-1025]
[11:51:03] [Server thread/INFO] [FML]: Itemstack injection complete
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_45]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_45]
at java.lang.reflect.Method.invoke(Method.java:497) ~[?:1.8.0_45]
at com.google.common.eventbus.SynchronizedEventSubscriber.handleEvent(SynchronizedEventSubscriber.java:47) [minecraft_server.1.8.jar:?]
at com.google.common.eventbus.EventBus.dispatch(EventBus.java:322) [minecraft_server.1.8.jar:?]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_45]
at com.google.common.eventbus.EventSubscriber.handleEvent(EventSubscriber.java:74) [minecraft_server.1.8.jar:?]
at com.google.common.eventbus.EventBus.dispatchQueuedEvents(EventBus.java:304) [minecraft_server.1.8.jar:?]
at com.google.common.eventbus.EventBus.post(EventBus.java:275) [minecraft_server.1.8.jar:?]
at net.minecraftforge.fml.common.LoadController.sendEventToModContainer(LoadController.java:212) [LoadController.class:?]
at net.minecraftforge.fml.common.LoadController.propogateStateMessage(LoadController.java:190) [LoadController.class:?]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_45]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_45]
at java.lang.reflect.Method.invoke(Method.java:497) ~[?:1.8.0_45]
at com.google.common.eventbus.EventSubscriber.handleEvent(EventSubscriber.java:74) [minecraft_server.1.8.jar:?]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_45]
at com.google.common.eventbus.SynchronizedEventSubscriber.handleEvent(SynchronizedEventSubscriber.java:47) [minecraft_server.1.8.jar:?]
at com.google.common.eventbus.EventBus.dispatch(EventBus.java:322) [minecraft_server.1.8.jar:?]
at com.google.common.eventbus.EventBus.dispatchQueuedEvents(EventBus.java:304) [minecraft_server.1.8.jar:?]
at com.google.common.eventbus.EventBus.post(EventBus.java:275) [minecraft_server.1.8.jar:?]
at net.minecraftforge.fml.common.LoadController.onPost(LoadController.java:53) [LoadController.class:?]
at net.minecraftforge.fml.common.LoadController.distributeStateMessage(LoadController.java:119) [LoadController.class:?]
at net.minecraftforge.fml.common.FMLCommonHandler.handleServerAboutToStart(FMLCommonHandler.java:314) [FMLCommonHandler.class:?]
at net.minecraftforge.fml.common.Loader.serverAboutToStart(Loader.java:851) [Loader.class:?]
at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:438) [MinecraftServer.class:?]
at java.lang.Thread.run(Thread.java:745) [?:1.8.0_45]
// I doesnt create the folder or am i sopost to create one then where
Pore currently doesn’t run on the latest Sponge builds. Read a few posts above.
1 Like
Will Pore continue for 1.8 and 1.8.9?