I want to write a widget that auto-resigns you when your fps gets below 10 during 8 seconds.
Since the MT client doesnt work, and the spring UI is unresponsive when having low-fps it's not playing a game but more being nearly a spectator looking at only your own base.
What is the code/commands for...
- checking current fps?
- resigning
- do a chat message to your team say "I was resigned by the auto-resign widget" or something
It's either:
- MT client working without crashes
- Having this widget availible,
- Having a (respoinisve) UI that is not bound/failing with by low fps
- quit playing
Auto-resign widget
Moderator: Moderators
- KingRaptor
- Zero-K Developer
- Posts: 838
- Joined: 14 Mar 2007, 03:44
Re: Auto-resign widget
I'd put the threshold lower, to <5 or so. I find the game is still mostly playable at ~10 FPS.
Anyway, to answer your questions in order:
Anyway, to answer your questions in order:
- Spring.GetFPS() (but this is apparently unreliable, you may want to calculate it based on frames/time elapsed instead. See this widget for an example).
- Spring.SendCommands("spectator")
- Spring.SendCommands("say I was resigned by the auto-resign widget")
- bobthedinosaur
- Blood & Steel Developer
- Posts: 2702
- Joined: 25 Aug 2004, 13:31
Re: Auto-resign widget
make it adjustable
Re: Auto-resign widget
Someone make 100 fleas and they cluster somewhere and make huge lag for 10 seconds BAM! everybody resigns win win.
Re: Auto-resign widget
I lol'd.wolas wrote:Someone make 100 fleas and they cluster somewhere and make huge lag for 10 seconds BAM! everybody resigns win win.
Re: Auto-resign widget
lol yes, ofc it would be adjustable to say like 60 seconds would be more appropriate.
Yes it can be abused or create other unwanted resigns, but heck, you can filter a lot of those too... but only required too much work I think.
I guess I don't want to have it that badly... or think that the widget is that worthy the community. Probably even unwanted by the devs if it gets more wide spread. (which prolly won't be the case at all anway)
oh and thnx KingRaptor for your quick response
Yes it can be abused or create other unwanted resigns, but heck, you can filter a lot of those too... but only required too much work I think.
I guess I don't want to have it that badly... or think that the widget is that worthy the community. Probably even unwanted by the devs if it gets more wide spread. (which prolly won't be the case at all anway)
oh and thnx KingRaptor for your quick response