|Anonymous | Login | Signup for a new account||2019-09-19 08:26 UTC|
|My View | View Issues | Change Log | Roadmap | Doomseeker Issue Support Ranking | Rules | My Account|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0002017||Doomseeker||[All Projects] Suggestion||public||2014-12-02 23:07||2019-03-26 18:32|
|Priority||low||Severity||minor||Reproducibility||have not tried|
|Target Version||Fixed in Version|
|Summary||0002017: Point games in configuration to different executables basing on version.|
|Description||We could allow an optional advanced setting in Doomseeker where user would be able to use different versions of games. Doomseeker would launch specific version basing on what version the server is, or revert to default one if specified.|
There are situations where the same master server returns servers that run different versions of the game. This usually happens during transition periods, but not always. For example, all 3 Chocolate Doom servers that are currently being reported by the master server run different versions of Chocolate Doom.
Doomseeker could be a front-end that, with some effort from the user, would bind these versions together and pick the best-fitting one for given server.
|I leave this here as an idea open for a discussion. Would something like that be useful?|
Sure, it could be useful. In general though it's not a huge issue. Although I haven't got a clue what's up with chocolate doom.
I usually hear this kind of idea brought up around transition periods (some people panic when a certain population have trouble comprehending the concept of an upgrade). To a point, I do wonder how feasible it would be to have Doomseeker be a central hub and "forgo" having people set up their source ports. That is have Doomseeker act as a package manager for everything Doom.
Possibly related to 0001961?
Pol M (developer)
|I'd say that this ticket is covered by 0001961, and I'd say that it's more comfortable by the end-user to simply let doomseeker handle everything. Also, since the clients are still accessible in their prefered location, they can use them there to play offline. It kinda is a better implementation than making the user manually enter client paths and keeping track of what client is which. Maybe not worth implementing?|
|Only registered users can voice their support. Click here to register, or here to log in.|
|Supporters:||No one explicitly supports this issue yet.|
|Opponents:||No one explicitly opposes this issue yet.|
|2014-12-02 23:07||Zalewa||New Issue|
|2014-12-02 23:08||Zalewa||Description Updated||View Revisions|
|2014-12-02 23:10||Zalewa||Note Added: 0011028|
|2014-12-03 01:08||Blzut3||Note Added: 0011033|
|2017-11-03 12:13||WubTheCaptain||Status||new => acknowledged|
|2017-11-03 15:05||Zalewa||Relationship added||related to 0001961|
|2018-10-05 08:43||WubTheCaptain||Priority||normal => low|
|2019-03-26 18:31||Pol M||Note Added: 0020459|
Questions or other issues? Contact Us.
|Copyright © 2000 - 2019 MantisBT Team|