Skip to content
This repository has been archived by the owner on Jan 28, 2022. It is now read-only.

Egg target km always 0 #64

Closed
Wroud opened this issue Jul 25, 2016 · 4 comments
Closed

Egg target km always 0 #64

Wroud opened this issue Jul 25, 2016 · 4 comments

Comments

@Wroud
Copy link

Wroud commented Jul 25, 2016 •
edited
Loading

Server response contains eggs have egg_km_walked_target and egg_km_walked_start is 0
Is this protobuff problem?
@Wroud Wroud closed this as completed Jul 25, 2016
@Wroud Wroud reopened this Jul 25, 2016
@Wroud
Copy link
Author

Wroud commented Jul 25, 2016

problem with variable type, egg_km_walked_target and egg_km_walked_start must be double, now its int32 fix plz

@vmarchaud
Copy link

???

@Wroud
Copy link
Author

Wroud commented Jul 26, 2016

oh sorry, have old version

@Wroud Wroud closed this as completed Jul 26, 2016
@vmarchaud
Copy link

But the problem is the same with double, the servers arent sending the egg_walked_start value so its always 0.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Wroud @vmarchaud