Seriosk
Programmer;
- Oct 29, 2016
- 256
- 105
What is Cascade?
Cascade is a Habbo Notification program that will send you notifications to the console window when new things happen involving your hotel... ye.. I know.. pretty damn simple and in some views pointless, but what the hell.. its something, and hopefully me or some other developer will maybe extend it and make it that little bit useful.
Development GitHub
Have fun, I have included the source so you guys can edit as you go along, didn't really put much effort in just had a spare hour to kill so thought I would make something simple, enjoy.. don't think I'll be pushing any updates for this after 3.0 unless anyone wants me to, but you can probably add other things such as notifications for other tables and what not
Also I know this isn't the best way to do this but its just an easy way for some people who just don't want to go to the trouble of setting up web sockets or anything like that... just edit config and go.
But Emulator Data is cached?
I know, if you want it to live-update then PM me and I'll give you the code to uncache the data that Cascade uses, other than that, you'll have to wait for a user logout and the emu to update the db... Everything else like bans, registrations, etc works just that the credits, pixels and other things involving the users table wont really be live because of the cached data..
UPDATE 1.1:
Just that sometimes data can be incorrect but usually 99% of the time its correct, for example if a machine was banned and there are two accounts online with that machine id, it might mistake the first one and the second one was actually banned..
Cascade is a Habbo Notification program that will send you notifications to the console window when new things happen involving your hotel... ye.. I know.. pretty damn simple and in some views pointless, but what the hell.. its something, and hopefully me or some other developer will maybe extend it and make it that little bit useful.
Development GitHub
-
You must be registered for see links
Have fun, I have included the source so you guys can edit as you go along, didn't really put much effort in just had a spare hour to kill so thought I would make something simple, enjoy.. don't think I'll be pushing any updates for this after 3.0 unless anyone wants me to, but you can probably add other things such as notifications for other tables and what not
Also I know this isn't the best way to do this but its just an easy way for some people who just don't want to go to the trouble of setting up web sockets or anything like that... just edit config and go.
But Emulator Data is cached?
I know, if you want it to live-update then PM me and I'll give you the code to uncache the data that Cascade uses, other than that, you'll have to wait for a user logout and the emu to update the db... Everything else like bans, registrations, etc works just that the credits, pixels and other things involving the users table wont really be live because of the cached data..
UPDATE 1.1:
- Improved query quality, faster and more specific i suppose...
- Can not get notified when a user enters the client (change of auth_ticket)
- Can not get notified when a user logs in (Change of last_online)
- Can now get notified when a user changes clothes (Change of look column)
- Can now get notified when a user tries entering and they are banned (change of auth ticket + ban = true check)
- Can now get notified when a new user is banned (checks for added records to ban table
- Improved a lot of the codes quality.
- Can now get notified when a user is ranked (change of rank).
- Can now get notified if a users credits change.
- Can now get notified if a users pixels change.
- Can now get notified if a users vip_points change.
- Can not get notified when a user changes their username
- Your now told if there is a new version of Cascade available for download.
- Ability to select different color text for each type of log
- Individual config settings for each type of log (not just cascade.disable_all_cache_checks)
- Automatic update feature, updates to the latest version
Just that sometimes data can be incorrect but usually 99% of the time its correct, for example if a machine was banned and there are two accounts online with that machine id, it might mistake the first one and the second one was actually banned..
Just want to clarify some things first.. so basically the timer interval basically determines the whole application, just make sure not to set it too low, I recommend 1000, I was able to get away with 200ms without it lagging, but I had like 10 users in my user table, for big hotels with a lot of users registered it may lag, it all depends on how fast your server is at executing MySQL querys, just try it and find a comfortable interval, obviously the lower it is, the faster you get updated.
You'll be told if your interval is too low because it will say "Timer is lagging" so ye, just make sure that isn't printing to the console.
You'll be told if your interval is too low because it will say "Timer is lagging" so ye, just make sure that isn't printing to the console.
Last edited: