Suggestion: Strange Sapper at 1.3–1.4 keys

Price Suggestion

~7.45 keys

195 votes up

25 votes down

Related Suggestions

This suggestion was accepted Fri, 01 May 15 22:10:38 +0000 by polar.

Comments can no longer be left on this suggestion.

Comments

Trying out carex’s outpost daemon, hope this goes well ;_;

http://tf2outpost.com/trade/25818909 - Created -1d/Last bumped -16m 1.4 autobump

http://tf2outpost.com/trade/25827043 - Created -2h/Last bumped -20m 1.44 young

http://tf2outpost.com/trade/25824710 - Created -10h/Last bumped -1h 1.3 (young)

http://tf2outpost.com/trade/25808115 - Created -2d/Last bumped -1h 1.3

http://tf2outpost.com/trade/25783157 - Created -5d/Last bumped -5h 1.3

http://www.tf2outpost.com/trade/25815731 1.16 (young, not using)

http://www.tf2outpost.com/trade/25605724 bp.tf 3 weeks

Keeping 1.4 in range as conservative drop, can’t even find 1.5 sellers

By "B" you mean bumped?...

It may sound professional but i think you should put a note saying what it is lol...

Sorry, forgot to edit that, it happened because I copy/pasted lol. Editing notes :]

Lol haha no problem, I just tried to help people who won't understand ;)

UC = Uncompleted

c = created

b = bumped

CONGRATS ON BLUE BELT :D <3

"carex’s outpost daemon"

Wat is this

https://github.com/caresx/outpostd

Up to you to know how to use it.

challenge accepted.

I know you don't really want to answer questions about it, but there are a few errors I'm having in it, particularly in the filters. I would truly appreciate your help. I noticed the examples have a lot of spaces where they shouldn't, this is possibly because I'm running it on a toaster(raspi linux), so it is a bit different, I'll try to see if this is universal when I can.

It's a bit confusing that the killstreak is under both item and its own attribute in the FILTERS.md file, but only under item in scand.js. For some reason !trade.premium in the example filters didn't work, I poked around but couldn't find a reason why, but the !autralium filter seemed to work. Really just looking for the killstreak filter, but it is unique in the way it works because active is under both item and killstreak. Here are a few of the many I tried.

./outpostd.sh -r -f "when.has(item,item.killstreak)" - removes all trades xD (not all of the scanned trades have killstreaked items from manual double check)

everything else had invalid syntax or no effect that I tried

./outpostd.sh -r -f "when.has(item.killstreak,active=active)”

./outpostd.sh -r -f "when.has(item,item.killstreak.active)”

./outpostd.sh -r -f "when.has(item,item.killstreak=Active)”

./outpostd.sh -r -f "when.has(item,item.attrs!==Killstreaks:Active)”

./outpostd.sh -r -f “item.killstreak:active !== active”

./outpostd.sh -r -f "item.killstreakactive !== active"

./outpostd.sh -r -f "when.has(item, item.killstreakactive)”

./outpostd.sh -r -f "when.has(item,item.killstreak,Active)"

./outpostd.sh -r -f "when.has(item.killstreak,active==1)" <—— really thought this one would work, doesn’t.

./outpostd.sh -r -f "when.has(item.killstreak,active==1)"

./outpostd.sh -r -f "when.has(item.attrs,item.killstreaks=1)”

./outpostd.sh -r -f "when.has(item,item.killstreak.active=1)”

./outpostd.sh -r -f "when.has(item,item.killstreak.active)"

./outpostd.sh -r -f “killstreak.active”

(quotes are messed up font here, don’t copy paste not that it works anyway.)

Thanks for your time, its fine if you don't want to deal with it I understand.

Since what you're doing is evaluating javascript when you use the -f option, you need to abide by the syntax rules. For what you're doing, you need:

./outpostd.sh -r -f "when.has(item, item.killstreak.active)" -> removes all killstreaks

For killstreak weapons only you will want to do:

./outpostd -r -f "when.has(item, !item.killstreak.active)"

Here, if any item on the has side is not a killstreak item, the trade will be discarded. If you want to ensure at least 1 item on the has side is a killstreak (otherwise discard the trade), you'll need to do something like this:

./outpostd.sh -r -f "(function () { if (!item.id) { return !!global.hasks; } else if (!global.hasks) { global.hasks = item.killstreak.active; return false; }());"

Thanks for clarifying, for some reason !events still don't work but I think that is just my computer. After reviewing the outpost-scanned.json file, the problem was actually in the scanning and not the filters. I have no clue what is causing that so I'll look more closely at it later when I have more time.