pk api/stream
pk api/stream
I wish someone would make a pk stream anytime anyone engages another pc, and it would stream information live or through an api. would be sick.
a STRONG player has killed a FADE in the NORTH, etc. example.
a STRONG player has killed a FADE in the NORTH, etc. example.
Re: pk api/stream
Hasp has died....again! Surprised?
Re: pk api/stream
It looks like the WoTMUD Imms twitter feed was doing this for a few months last summer. Seems kind of pointless to me.
https://twitter.com/wotmud?lang=en
https://twitter.com/wotmud?lang=en
Re: pk api/stream
Was on longer than a couple months iirc... stopped last November. Wish Flash would turn it back on. Don’t think there was a post on why it stopped.
Re: pk api/stream
Wonder what's the classification of "skilled", "elite", and "powerful" used there.
Was thinking "clanned rank 5 and down", "clanned rank 6", and "clanned master"
Was thinking "clanned rank 5 and down", "clanned rank 6", and "clanned master"
Re: pk api/stream
If we're proposing solutions that required coding Elite = tav sei or reaver skilled = greater than 250 tps. No descriptor = everyone elseQuantalex wrote:Wonder what's the classification of "skilled", "elite", and "powerful" used there.
Was thinking "clanned rank 5 and down", "clanned rank 6", and "clanned master"
Probably the best and most equitable metric as it separate people based on both ability to get kills and ability to not get killed.
Re: pk api/stream
If we're proposing solutions that require coding, then completely changing how TPS are calculated would be preferable to twitter noise. Kinslayer does a decent job of it, focusing on getting kills and being able to view tps gained per week, month, year. Instead of focusing on conservatively hoarding tps type of playstyle.daal wrote:If we're proposing solutions that required coding Elite = tav sei or reaver skilled = greater than 250 tps. No descriptor = everyone elseQuantalex wrote:Wonder what's the classification of "skilled", "elite", and "powerful" used there.
Was thinking "clanned rank 5 and down", "clanned rank 6", and "clanned master"
Probably the best and most equitable metric as it separate people based on both ability to get kills and ability to not get killed.
Re: pk api/stream
Sounds like a marvelous idea. I have never been terribly fond of tps in general. I mean if a scrublord like me can briefly make the taveren list for a single lucky kill (true story, this actually happened) there is something wrong with how those "legends" are calculated.Maegon wrote:If we're proposing solutions that require coding, then completely changing how TPS are calculated would be preferable to twitter noise. Kinslayer does a decent job of it, focusing on getting kills and being able to view tps gained per week, month, year. Instead of focusing on conservatively hoarding tps type of playstyle.daal wrote:If we're proposing solutions that required coding Elite = tav sei or reaver skilled = greater than 250 tps. No descriptor = everyone elseQuantalex wrote:Wonder what's the classification of "skilled", "elite", and "powerful" used there.
Was thinking "clanned rank 5 and down", "clanned rank 6", and "clanned master"
Probably the best and most equitable metric as it separate people based on both ability to get kills and ability to not get killed.
Re: pk api/stream
I think skilled, elite, powerfull was level range, I'm not sure what levels though. Maybe 30-39, 40-49 and 50-51. Thuvia might know, or any immortal could tell you. I think the twitter posts were a channel that immortals can see and Flash hooked it up to the twitter account. It spammed the hell out of the twitter feed at first. Then he coded something to slow it down to only couple an hour or something, also had a delay.Quantalex wrote:Wonder what's the classification of "skilled", "elite", and "powerful" used there.
Was thinking "clanned rank 5 and down", "clanned rank 6", and "clanned master"
Re: pk api/stream
Pretty sure the Twitter thing was shut down due to that pre-death kill bug that would crash the mud and save the soon-to-be dead? Did they try to fix it unsuccessfully so just turned it off?