-
Notifications
You must be signed in to change notification settings - Fork 30
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
Node drawing #75
Comments
The wrong placement of player names is caused by dsfix. DSCM just enables a feature that is already in the game, but that feature gets confused by dsfix.
Yes, that's how it's supposed to be 😉 |
@Wulf2k you seem to have some asm in place to at least change the displayed text. Maybe it would make more sense to set all text to the empty string instead, as the broken display is not very useful? |
well, i can alt+tab and look into DSCM window, sort by name, seek my enemy in the 'Active' tab. It's just a question of time. And i can do it pretty fast to be fair. But it would be great if i can just hit the Ctrl+1 and look into overlay. Why not? |
Because that is cheating. You are not supposed to know your enemies soul level, and he does not know yours. It's hard to stop people from abusing DSCM the way you do without breaking its functionality, but that's no reason to actively support that. |
I'd be willing to consider that, but I'd think it would just make more sense for anybody that's not running in 1280x720 to just not use node-drawing until I can figure out a replacement system for the built-in node drawing. At least if the names are offset you can still check for a specific name at a glance. I don't expect people really care "which" circle somebody is. |
For some reason, this fiture looks awful on my computer. Have no idea, why is that and what information i should provide to you.
This is how it looks to me.
Also, if you will look into this part of code, could you please add player SL to his name in the node drawing overlay? Atm there is no fast way to know what SL of your enemy when you do/get invasions.
The text was updated successfully, but these errors were encountered: