Bukkit

@Madminor

It's The Spark - Digital Blasphemy, I think.

https://chrome.google.com/webstore/detail/the-spark-digital-blasphe/lhkknnebkjlngeopapiainhbhkeeihkk?hl=en

Version WebSocketServices v1.2.0-R6 is pending, which contains the new player service and upgraded to use bukkit 1.5.1-R0.2.

@nullschritt

Hi Nullschritt,

I would rather the plug-in be in a stable, beta state before I release it, it's just sort of my obsessive need to have stable working products. :P An experimental build, and the code is all available on github.

https://github.com/CaffeinatedRat/Spectator

@PP19

PP19,

You can find all the experimental build and the client-side script at github at the following location:

https://github.com/CaffeinatedRat/Spectator/tree/master/build

Again, remember this is experimental, so there are still bugs that are present and the data being sent between the server & the client is not optimized, so there are performance issues. Also, with it being experimental, the camera will always take the location of the first player that bukkit returns, which is not necessarily the first person who has logged in, but just how bukkit sorts player's names. There is also no defined behavior for alternate environments, such as The Nether or The end.

@sp0ng3b0b

Hi sp0ng3b0b,

It is possible, but it'd have to be a WebSocketServer extension. I have thought about writing one for a while, but two issues must be addressed first.

1) There are currently a few security issues with WebSockets. For one, creating such a plug-in creates a tunnel to your server giving anyone direct access as opposed to an additional layer of security that a host provides hiding it within a secure server. While there is a white-list feature with this plug-in, anyone who is capable and intelligent enough can spoof the origin and circumvent the white-list; this is a flaw of the WebSockets technology itself. The white-list is currently nothing more than a deterrent. Another issue is this plug-in does not support SSL for websockets, and even if it did, most people would not be willing to spend the monthly expense for a cert. Currently this plug-in only performs read-only queries, which can expose information about someone's server, but does not allow anyone to change the state of the server. This wouldn't be the case with an extension that provided admin tools. Finally, an authentication mechanism would have to be created, so that an admin would have to log-in to their server before they could change server states; furthermore, since it would be a non-ssl log-in, it would be susceptible to man in the middle attacks, where skill exploiters could capture your log-in info and take control of your server. Of course, this is a vulnerability of any website that does not use a SSL log-in in the first place.

2) The next issue deals with the fact that this plug-in is designed mostly for developers. Most websites are not driven by client-side scripting, but this plug-in is, so any user would have to have a website already in place and would have to modify that website to take advantage of the client-side nature of the plug-in. While this works great for people that already have websites in place, it doesn't work well for those that are starting from scratch and do not know how to create a website or integrate this tool into said website. I've tried to make this plug-in as user friendly as possible, even for those that have no knowledge of web development, but it really isn't enough.

I still plan on developing a simple admin tool, but it will have to be an extension, so that this plug-ins main functionality remains as read-only queries.

By the way, if you are a developer, there is a way to write extensions to this plug-in. The experimental plug-in spectator, is an extension to the WebSocketServer and provides some limited examples as to how to add create your own extension or even extend current plug-ins to use the WebSocketServer.

Hopefully this is enough to answer your question, and I am sorry I do not already have such functionality available. It would be if it was a trivial matter.

@PP19

Hi PP19,

The Spectator plug-in is in an experimental state and is not ready for use; however, I can still provide you with client-side code for you to review.

@Lolmewn

Excellent, let me know if you need any help or have any issues. I don't believe I have the WebSocketService extension development documented that well yet.

Version WebSocketServices v1.2.0-R5 is in development. The following changes will be included in the new version:

• Upgraded to use CraftBukkit 1.5.1.
• Added a new player service to provide details on an individual player.

Version WebSocketServices v1.1.9-R4 is pending to hopefully fix an issue addressed in ticket Time Issue.

Started documenting the client-side library WebSocketServices.min.js, which can be found at

WebSocketServices.min.js Client-Side API

@rulystarw

Hello Rulystarw,

You can start by taking the HTML in the Client-Side/example/fancy folder and copy everything in that folder to any webserver that you have. It should run as is, as long as you are running it on a webserver. Next, modify the minecraft.js under the folder Client-Side/example/fancy/js and change the websocketAddress to yours, as shown below:

wss = new CaffeinatedRat.Minecraft.WebSocketServices({
  //Your websocketAddress below
  websocketAddress: 'ws://minecraft.caffeinatedrat.com:25564'
});

I'm sorry it's not that detailed, but I have not had time to document step-by-step instructions on how to setup the example website on a webserver.

@jeracom

Looks like you've helped me discover another small bug. See the ticket. I'll have this fixed in 1.1.8.

http://dev.bukkit.org/server-mods/websocketservices/tickets/5-plugin-services-are-blank-again-with-the-plugin-lockette/