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

Radar Drawing empty #34

Open
UtkaUtochka opened this issue Oct 18, 2024 · 5 comments
Open

Radar Drawing empty #34

UtkaUtochka opened this issue Oct 18, 2024 · 5 comments

Comments

@UtkaUtochka
Copy link

Снимок экрана 2024-10-18 173036

@UtkaUtochka
Copy link
Author

I'm stupid, everything works

@Z-Foster
Copy link

What was the fix?

@abrahambunsen
Copy link

Please I have the same issue but im not able to figure out whats wrong. @UtkaUtochka how did you solved it my man?

@UsamShehata
Copy link

dude how did you solve it?

@pcorezzola
Copy link

Nothing is displayed because there was a change in the event code (EventCodes.js).
When a resource, a player, etc., "appears," notifications are sent to the app, allowing it to display them on the map.
Each "notification" has a number that identifies what the change or information will be. The problem arises because the numbers for each event have changed, so the app doesn't know what to do in that case or confuses it with another action.

The change isn't that big. For example, when the game had a "list" of resources (Wood, Rock, etc.) appearing in the game, it sent a notification with the number 38. However, now it sends the same content with the number 37. But the app expected to do something different for that number, and 🤯🧨.

It doesn't end there. Previously, when a player appeared on screen, the game sent a notification with the number 28. Now it does so with the number 29, but that's not the serious part—apparently, it no longer provides the player's coordinates. So, displaying them on screen becomes complicated (I’d say almost impossible without making more changes).

I played Albion a bit some time ago, revisited it to see how things were going, and came across this awesome tool. Unfortunately, when I tried it, I got the same error as you 😭.

I forked the repository in case you'd like to see or get solutions before the creator comes up with a definitive fix. I found how this all works quite interesting—if I have some time in the next few days, I might try to improve the situation.

Best regards!

image

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

No branches or pull requests

5 participants