MOB.CODES - Punch Here!
Forums › General Discussion › MOB.CODES - Punch Here!-
★★BЯOШИИOTΞ★★ wrote:
I agree your a good boy brownnote, i good smart boy.pugshark wrote:
You're welcome again.Bump
Thanks again for the site brownnote. -
Some Mickey Dunn guy asked for new temp code notifications. Follow @turfwarswiki on Twitter if you want to feed your addiction RIGHT NOW!!!!
I promise I won't throw in a few extra chirps at 3AM (often).
Seriously, thanks for the suggestion, though. Doing battle with Twitter OAuth was a challenge. He was over Unger, and I was under Dunn.
-
In case you are wondering about the timing... Why it's off by up to an hour... I'll tell you. (Because I know you will ask Viper.)
The site polls Turf Wars every hour on the hour for temp codes. Every time I do it, it dumps the entire set in the database, and deletes expired codes. If the code is already there, it just leaves the original. It's not really that smart about it. It doesn't care if there are new codes or not.
So how do I know when new codes come out without bothering to look for them? Nick provides a time stamp that dates the "set" in the data. When the hourly job runs, if that time stamp is within 3600 seconds of now, the script tweets it out. He also includes a time stamp for the next update, which I include in the tweet for informational purposes.
So if his set is updated at 9:02:15 one evening, I won't get them until 10:00:00 on my site. But at 10:00:00 a tweet goes out that will say there was a new set: 9:02:15.
Pro tip: Use your clock app to show UTC time.
-
Thanks a ton Brown!
-
I keep getting error logging in..
-
Punch all new codes. Great site BN
-
Ese Santos wrote:
What error you got?I keep getting error logging in..
-
★★BЯOШИИOTΞ★★ wrote:
Its cool brown i got in. Thx for replying🍻🍊Ese Santos wrote:
What error you got?I keep getting error logging in..
-
Brownnote...I've been using your site and making progress, thanks again for the effort.
I have a question though and im not sure if it has already been asked...
How many strikes does a contributor get putting in bad/fake codes before they are warned, removed or however you go about handling that?
To be honest it hasn't been that bad, one or two here and there (seems pretty normal ratio wise) but, sometimes it's the same players and Im curious.
-
〓 CANDO 〓 wrote:
I'm not automatically booting people for bad codes. It's a manual process.Brownnote...I've been using your site and making progress, thanks again for the effort.
I have a question though and im not sure if it has already been asked...
How many strikes does a contributor get putting in bad/fake codes before they are warned, removed or however you go about handling that?
To be honest it hasn't been that bad, one or two here and there (seems pretty normal ratio wise) but, sometimes it's the same players and Im curious.
-
〓 CANDO 〓 wrote:
Really? Usually im getting 1-2 bad codes a pageBrownnote...I've been using your site and making progress, thanks again for the effort.
I have a question though and im not sure if it has already been asked...
How many strikes does a contributor get putting in bad/fake codes before they are warned, removed or however you go about handling that?
To be honest it hasn't been that bad, one or two here and there (seems pretty normal ratio wise) but, sometimes it's the same players and Im curious.
-
💣KA-BOOM💣 wrote:
^〓 CANDO 〓 wrote:
Really? Usually im getting 1-2 bad codes a pageBrownnote...I've been using your site and making progress, thanks again for the effort.
I have a question though and im not sure if it has already been asked...
How many strikes does a contributor get putting in bad/fake codes before they are warned, removed or however you go about handling that?
To be honest it hasn't been that bad, one or two here and there (seems pretty normal ratio wise) but, sometimes it's the same players and Im curious.
-
The ones I've seen typically haven't been by the same player. (The code often becomes bad when the player buys a custom code.) The only difference I see from ICM is that it takes longer for codes flagged bad to be removed.
However, the other day I noticed a one player had entered several bad codes. I just pm'ed the player & asked them not to enter random codes & explained where to find codes. The player thanked me & explained they thought they were just supposed to make up their own numbers. (No, I didn't ask why they thought this or why they didn't read Brown's info on the add page. I was just happy they were receptive to my request & explanation.)
-
My pet peeve is when someone enters a non-custom code that is only 7 characters. All regular codes are 8 characters. It should be obvious that the code is wrong unless they've just accidentally hit the "Add" button before they were finished entering the code.
-
fun6754 wrote:
^^💣KA-BOOM💣 wrote:
^〓 CANDO 〓 wrote:
Really? Usually im getting 1-2 bad codes a pageBrownnote...I've been using your site and making progress, thanks again for the effort.
I have a question though and im not sure if it has already been asked...
How many strikes does a contributor get putting in bad/fake codes before they are warned, removed or however you go about handling that?
To be honest it hasn't been that bad, one or two here and there (seems pretty normal ratio wise) but, sometimes it's the same players and Im curious.
Do you mark them bad? -
@Brownnote...Yes but, first I re-type it and double check that, I didn't misspell it myself. Then I hit the check box.
-
〓 CANDO 〓 wrote:
@Brownnote...Yes but, first I re-type it and double check that, I didn't misspell it myself. Then I hit the check box.
-
Excellent. Gold stars for everyone! 🌟
-
1. Love the new site, especially the little sayings that appear randomly at the bottom of the punch page :-)
2. I usually get 1-3 bad ones per 10. I double check first, then check them off. Was curious too as to how many checks removed something.
3. Any way we can "go back" if we accidentally skip a page by any chance? Hit the button twice accidentally.Have punched about 1200 in 2 days :-)
-
jenni guadagno wrote:
1. Thanks!1. Love the new site, especially the little sayings that appear randomly at the bottom of the punch page :-)
2. I usually get 1-3 bad ones per 10. I double check first, then check them off. Was curious too as to how many checks removed something.
3. Any way we can "go back" if we accidentally skip a page by any chance? Hit the button twice accidentally.Have punched about 1200 in 2 days :-)
2. Strike 3! You're outta there!
3. I don't think there's a way to go back once you hit the button, unless your browser lets you go back. The site is like a code fire hose. It doesn't know which water didn't get you wet.
-
Not to get too techie in here but what records what u have and haven't punched already? Trying to see if there's a way to trick it to let me go back to those codes. Cookie, session, db?
Oh and I saw one issue happening w my super rapid entering. If u enter a set of 10, and u click the button, if someone had entered any new ones while u were entering ur 10, u never see them and they are marked as punched. U can tell because the bottom ones u just did show up at the top of the new set of 10 like they're num 11 and 12, etc. just FYI :-)
-
The codes you punch are thrown on a big pile in your own indexed table of punched codes. There's no way to distinguish when they were punched, how many are in a set, or if they were not punched yet. There's no danger of missing any new codes though.
-
Ok thanks for the info Brown! :-)
-
I'm punching invalid codes that date but to as long as 2 months ago; how often do you check the reports and action them?
-
ԲՄՐɿԾՄՏ wrote:
I do it every Festivus eve. I pour my concrete and set the Festivus pole. Then, I open the database to allow for the airing of grievances. I take the resulting list and apply the feats of strength in a metered fashion. It's all very ritualistic.I'm punching invalid codes that date but to as long as 2 months ago; how often do you check the reports and action them?
-
ԲՄՐɿԾՄՏ wrote:
Here's the thing. There are codes with one or two strikes, hundreds of them, that go all the way back to May. As soon as a code gets three strikes, it's out within an hour automatically. I can think of a two reasons old codes might not have 3 strikes yet.I'm punching invalid codes that date but to as long as 2 months ago; how often do you check the reports and action them?
1. Most people don't mark bad codes as bad, leaving the one or two people that do hanging.
2. Old codes can suddenly go bad when someone buys a custom code, or otherwise changes their code.
I am working on a support ticket system and knowledge base to answer these types of questions. Stay tuned.
-
★★BЯOШИИOTΞ★★ wrote:
I appreciate the response, I just seem to be getting at least 3/25 per page which ends up being a pretty annoying time sink trying to double/triple check that I haven't made a human error on my end.ԲՄՐɿԾՄՏ wrote:
Here's the thing. There are codes with one or two strikes, hundreds of them, that go all the way back to May. As soon as a code gets three strikes, it's out within an hour automatically. -snip-I'm punching invalid codes that date but to as long as 2 months ago; how often do you check the reports and action them?
Would it be possible (Just a suggestion), to have a automated system where as if a code is marked twice in X amount of minutes/hours, it automatically gets removed? This may help address the issue for future codes being added, although it will still rely heavily on user input to actually mark bad codes.
-
3 strikes is fair. I am guilty of not marking a code bad because I didn't know how much 1 "strike" mattered, and I didn't want to risk knocking someone out if I made a typo.
I'll mark them from now on.
I agree the risk of old codes being bad is higher. After the daily punchers have gotten past them, if they reset and change codes or get a custom code, there is likely to be less traffic on the old code lists than there are within the first 3-4 days of a code being added when the compulsive punchers get them.
Likewise, they are likely to be valid at that time too, it can take 4 months to get enough free don points from flurry to change your code.
-
Chucky Pancamo wrote:
I don't think strikes penalise the player adding them, it just simply means the code will be removed from the database. Being penalised for someone changing their mob code or for a simple typo would be to far fetched.3 strikes is fair. I am guilty of not marking a code bad because I didn't know how much 1 "strike" mattered, and I didn't want to risk knocking someone out if I made a typo.
I'll mark them from now on.
I agree the risk of old codes being bad is higher. -snip-
It's more of a community thing though, I mean, 3 people marking a code as bad to get it removed isn't asking for much and I'm sure more than 3 people are actually doing this.
-
Yeah, I didn't mean getting the contributor in trouble. I meant possibly causing someone with a valid code having their code removed, denying him of invites and us of a mobster to invite. Like if it was just one "invalid" and I was mistaken. 3 is good.
![[][]](https://turfwarsapp.com/img/app/ajax-forbutton.gif)
Purchase Respect Points NEW! · Support · Turf Map · Terms · Privacy
©2021 MeanFreePath LLC