[Pre-Release] Would anyone want/need this? (live serverfeed)

Would people be interested in a live server-feed that's easy to implement on any server - even binaries.

I've gotten it to run perfectly fine on a binary setup, and also on some random source I downloaded (Trinity I believe). It's not source dependant except for saving data to your database, which is a 2-line-of-code function.


Example of what this demo server below contains, which took me about 10 minutes to add.

• Player Login
• Player Logout
• Player Leveup
• PlayerX kills PlayerY
• Lottery winnings
• Boss kill (Banshee etc)
• Create guild
• GuildX has allied GuildY
• Guild pole taker
• Guild war winner

Ofcourse, anything can be added. It's just a matter of saving down a textstring to your database, the rest is handled automatically by PHP/JS.


Demo:

It's pretty simple to do but I always appreciate javascript/php examples because I'm shit when it comes to web dev. Like... I sorta know what I'm doing but I tend to end up frustrated instead ahah

Quote:

Originally Posted by pro4never It's pretty simple to do but I always appreciate javascript/php examples because I'm shit when it comes to web dev. Like... I sorta know what I'm doing but I tend to end up frustrated instead ahah

Yup, very simple. Just save data to a record-table, if binaries you'll have to do it via cq_action I believe. Read the data with AJAX with an interval, if new data present it with an effect.

It's a really nice addon though and so far I haven't seen anyone have this, so why not.

That's pretty cool yo'

Not really interested in it, but it's cool.

It's interesting, but it seems incomplete. It's just a webpage, right? This could be done using WPF and C#, linking the window to the side of the Conquer Online client (making it so it's always just to the right / side of the client). You can still use web data, just make it a program that runs along side the conquer window. I think it'd look a lot cleaner and more desirable that way. Otherwise, it looks great (not something that I would use, but maybe something others would use).

Quote:

Originally Posted by Fаng It's interesting, but it seems incomplete. It's just a webpage, right? This could be done using WPF and C#, linking the window to the side of the Conquer Online client (making it so it's always just to the right / side of the client). You can still use web data, just make it a program that runs along side the conquer window. I think it'd look a lot cleaner and more desirable that way. Otherwise, it looks great (not something that I would use, but maybe something others would use).

The point is to show it on the webpage, not to everyone currently playing.

Why would you want to see lottery winnings, guild winners etc. when you can see in in-game. The point behind it is to make the CO websites a little better because right now the standard is crap.

Quote:

Originally Posted by 'Emil The point is to show it on the webpage, not to everyone currently playing. Why would you want to see lottery winnings, guild winners etc. when you can see in in-game. The point behind it is to make the CO websites a little better because right now the standard is crap.

Oh, I thought it was just an example. I was more thinking of expandability. If it's just a website, then yah - it's great. It reminds me of some minecraft servers (how they do the text thing and all of that).

This is really badly thought out, the website should never be directly interacting with the live server database, if you want to do this sort of thing, have a batch that copies data from the game server to a database on the webserver, then have this script running.

Quote:

Originally Posted by Korvacs This is really badly thought out, the website should never be directly interacting with the live server database, if you want to do this sort of thing, have a batch that copies data from the game server to a database on the webserver, then have this script running.

And why is this, according to you. It's only fetching data and a server can handle a query every 3 seconds or so just fine. It also clears the table from old data.

What happens if the server goes down, how does the script react to that? My experience being that your website looks awful when things dont load correctly because of time outs, the solution is to switch to a more push orientated application, than pull such as this.

Quote:

Originally Posted by Korvacs What happens if the server goes down, how does the script react to that? My experience being that your website looks awful when things dont load correctly because of time outs, the solution is to switch to a more push orientated application, than pull such as this.

Do you mean the gameserver or the host? In PHP you can easily check the status of the database connection, if none is made then simply don't return any data to the AJAX-call and it won't show you any error messages.

You could also have another AJAX-timer running every x-second to ping the server with a timeout, if fails then stop the timer. Two solutions that takes under a minute to implement, so I don't really see your point sorry.

Quote:

Originally Posted by 'Emil Do you mean the gameserver or the host? In PHP you can easily check the status of the database connection, if none is made then simply don't return any data to the AJAX-call and it won't show you any error messages. You could also have another AJAX-timer running every x-second to ping the server with a timeout, if fails then stop the timer. Two solutions that takes under a minute to implement, so I don't really see your point sorry.

The gameserver which hosts the database, obviously. And those are great, however they will need to timeout as I said, making the website hang effectively for several seconds before giving up.

Also neither of those are implemented in this, so this is badly thought out as I said.

I really don't think you know how this works, do you.

First of all, if the gameserver goes down that's fine. The host hosts the database, not the gameserver, correct? If the gameserver goes down, the script will continue to try and fetch new data (as it would if it were online). This timer could easily be stopped with the ping method, as I said. If the host itself goes down, this can be stopped via PHP as it won't be able to connect to the database.


AJAX stands for Asynchronous JavaScript and XML. The website itself won't "hang effectively for several seconds before giving up", if it fails to fetch data.

Sorry, I'm classifying the gameserver as the host in this instance, since host implys the webserver's host.

The Ajax aspect is fine, its the rest that is going to give up on you.