Price guide numbers abnormally off

[Piotr]

If people don't ask doubts or comment on things that are not working as they should, the app will not improve as fast as it could, and that's bad for everyone (customers and developer).

On the other hand, if people ask dumb questions which require minimum effort to figure the answer for, or if they mislead me into thinking something is terribly messed up in the app and thus force me to drop everything and go and try to fix this, that is time I can never get back, and believe me I'm stretched very thin at the moment. I don't think asking to be precise when posting in the iMtG section is too much, or hostile.

[swallowtail]

I would name the topic 'issues with price guide' or 'some prices are way off', but never 'terribly messed up'. I prefer precise wording in places which are visible to other customers, especially iMtG section of Gathering. I felt like a punishment is in line but one of the mods judged otherwise, fair enough. Now I made myself clear, if you post FUD here you will get harsh response from me. If you want to emo quit over it, you're free to go.

Ah Piotr, as they say down here "lighten up mate". Not just here in this thread, but in general when people ask questions.

The vast majority of respondants (your customers) in this thread disagree with you but I'll give you points for... let's call it 'tenacity'.

And when we point out that it's making some feel like it is not a comfortable place, you start talking about people emo quitting. LOL...

In the interest of no longer wasting my breath when it appears that you can't see anyone's point of view but your own (or just unwilling to acknowledge any but your own?), I will make one final observation:

Saying "sorry, I over-reacted" would probably gain you back more respect than you have lost in this. My mum always taught me that it takes personal backbone, courage and emotional intelligence to apologise, but that it makes you the better man for it.

To all those who have thanked my posts and +'ed karma for them in this thread, thank you. Respect to you.

[Mentonin]

Piotr, if you care so much for customers who might have a bad idea of the app reading this forums, try being nicer with your answers as well. The OP was just trying to report a problem to make the app better, and as he saw some messed up pricing, by 490 times the real price in the extreme one, he saw that as terrible. He didn't check every card, just saw some and reported, and I think it is was too messed up as well to have this values. If you want better titles, make a help posting etiquette (I would suggest something in the lines of 'problem with *section of the app here*', as it is pretty straightforward and make no misinterpretations.
Now, if logic is the ultimate law, what is the logic in flaming your own customers, specially the ones interested in making the app better and/or improving your own forum?

[Piotr]

Piotr, if you care so much for customers who might have a bad idea of the app reading this forums, try being nicer with your answers as well. The OP was just trying to report a problem to make the app better, and as he saw some messed up pricing, by 490 times the real price in the extreme one, he saw that as terrible. He didn't check every card, just saw some and reported, and I think it is was too messed up as well to have this values. If you want better titles, make a help posting etiquette (I would suggest something in the lines of 'problem with *section of the app here*', as it is pretty straightforward and make no misinterpretations.
Now, if logic is the ultimate law, what is the logic in flaming your own customers, specially the ones interested in making the app better and/or improving your own forum?

The etiquette we have on this forum is this: do not do to others what they would not want to be done to themselves. As one of 'others', I simply state a fact that I find this topic's thread to be false. False is the opposite of true, and something not true is a lie. I have no idea why people overreact to a harshly simple 'How is this not a lie?'. You don't want to see me talking, go and Hide me, if you disagree Don't, if you Like you know what to do, as simple as this is our etiquette Enjoy my forum

[MuggyWuggy]

Who cares anymore? the database is updated and prices arent in full retard mode.

Writing paragraphs hasn't solved anything in this Mexican standoff. I don't care anymore. The creator of the app said he was butthurt by my wording. I apologize that i offended you. I'm not going to play with these faerie .politics. of online forums. I use this app for trading, so if the prices are completely off when I'm trading a revised dual land, I'm going to inquire in my own manner and wording. Your app is great, it's not god like however, it is prone to error.

[Mentonin]

It is not just the 'how is it not a lie' from this thread. It is a series of harsh, filled with sarcasm, uncaring answer to posters not doing anything to really deserve it. I got a recent example quoted down here, but I can look for more if you want proof of it being a sequence

Yeah. In trying to use the predicate which I think is SQL or whatever which I've no clue about.
Put in this in to try to do it

SUBQUERY( bindernames, $x, $x.binder.name = 'Complete Collection ).@count = 0

Complete collection is my binder name so I can search just that. I check it it says looks ok but then click back and the app crashes

Well it should, you created properly broken predicate and the check is very dumb. Try this:

SUBQUERY( bindernames, $x, $x.binder.name = 'Complete Collection' ).@count = 0

and this

SUBQUERY( bindernames, $x, $x.binder.name = 'Complete Collection' ).@count > 0

You can save these as Bookmarks and that's it, iMtG can do what you wanted already.

darkshank was honestly trying to help. He stated that he didn't know exactly what he was doing, and gave a base for the other to 'try to do it', in his own words. He also stated that something in it was wrong, alright. Now, you corrected him, which was very nice, but did you have to say 'Well it should, you created a properly broken predicate and the check is very dumb'? Maybe just saying that there were some syntax errors would be nice. Using your own law, I bet darkshanx didn't want someone to say that something he did trying to help shouldn't work because it is very dumb

[Piotr]

Who cares anymore? the database is updated and prices arent in full retard mode.

Writing paragraphs hasn't solved anything in this Mexican standoff. I don't care anymore. The creator of the app said he was butthurt by my wording. I apologize that i offended you. I'm not going to play with these faerie .politics. of online forums. I use this app for trading, so if the prices are completely off when I'm trading a revised dual land, I'm going to inquire in my own manner and wording. Your app is great, it's not god like however, it is prone to error.

I apologise for being too harsh.

I do realise it is prone to error, fixing this is on my TODO. It's not a small task though as I need to rewrite a lot of TCGplayer.com unless they stop butthurting me by delivering dodgy prices.

[Piotr]

It is not just the 'how is it not a lie' from this thread. It is a series of harsh, filled with sarcasm, uncaring answer to posters not doing anything to really deserve it. I got a recent example quoted down here, but I can look for more if you want proof of it being a sequence

Yeah. In trying to use the predicate which I think is SQL or whatever which I've no clue about.
Put in this in to try to do it

SUBQUERY( bindernames, $x, $x.binder.name = 'Complete Collection ).@count = 0

Complete collection is my binder name so I can search just that. I check it it says looks ok but then click back and the app crashes

Well it should, you created properly broken predicate and the check is very dumb. Try this:

SUBQUERY( bindernames, $x, $x.binder.name = 'Complete Collection' ).@count = 0

and this

SUBQUERY( bindernames, $x, $x.binder.name = 'Complete Collection' ).@count > 0

You can save these as Bookmarks and that's it, iMtG can do what you wanted already.

darkshank was honestly trying to help. He stated that he didn't know exactly what he was doing, and gave a base for the other to 'try to do it', in his own words. He also stated that something in it was wrong, alright. Now, you corrected him, which was very nice, but did you have to say 'Well it should, you created a properly broken predicate and the check is very dumb'? Maybe just saying that there were some syntax errors would be nice. Using your own law, I bet darkshanx didn't want someone to say that something he did trying to help shouldn't work because it is very dumb

The predicate was properly broken. Not terribly 'Proper' in UK English is not hostile.

The check is the Check button in Predicate view, and it is truly dumb. I know, I wrote it, I'm not taking offence as this is the truth

[Mentonin]

I'm sorry, I thought you were talking about his SQL card check, not the check button. This proves how you can misunderstand things, specially in written communication. I can still compile the series, though. I saw you apologized, it is good, but do try to make a change, it is not that hard. And the other points in my post, though the example wasn't the best, are still valid

[Piotr]

Yes, but I'm a little bit evil Thank you for the advice.