Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Possible bug] Having buying orders makes script to stop working properly. #14

Closed
Tomasety-III opened this issue Apr 25, 2017 · 3 comments
Labels

Comments

@Tomasety-III
Copy link

This comes from my closed issue #11

I will try to explain once more.

Having buying orders at the same time as selling items listed on market can break script functionality.

It happens at least when the following requisite is met.

If a buying order has its first string with a higher sorting priority than the first string's item listed on market then script stops to work properly.

For example.

https://i.imgur.com/UaAcaID.png
The first item on my selling listing table (I don't know why script mixes buying orders and selling orders on the same table) is a buying order whose first string is a number 2.
Second item is a selling order listed whose first string is a a colon => ":"

Since a number goes first before a letter and a symbol in an ascendant alphabetic sorting then the first buying order has top priority on my selling listing. That's the cause which makes script to stop working as you can see on the picture. ( No green price section is highlighted)

But if I remove that first buying order (you can see on the next picture: https://i.imgur.com/GLmBU7g.png) then I can see how script works till it finds next buying order on my selling items list and in that case stops to working once again

Thanks once again @Nuklon

@Tomasety-III Tomasety-III changed the title [Possible bug] Having certain buying orders makes script to stop working properly. [Possible bug] Having buying orders makes script to stop working properly. Apr 25, 2017
@Nuklon
Copy link
Owner

Nuklon commented Apr 25, 2017

Ah, alright, I think I get it now, I'll investigate.

@Nuklon Nuklon added the bug label Apr 25, 2017
@Nuklon
Copy link
Owner

Nuklon commented Apr 29, 2017

I can confirm this is broken indeed, I'll see if I can fix this one too.

@Nuklon
Copy link
Owner

Nuklon commented Apr 29, 2017

Also fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants