Zandronum Chat on our Discord Server Get the latest version: 3.2
Source Code

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0003555Doomseeker[All Projects] Suggestionpublic2018-10-20 06:062018-11-02 09:46
ReporterZalewa 
Assigned To 
PrioritynoneSeverityfeatureReproducibilityN/A
StatusclosedResolutionsuspended 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version 
Summary0003555: Consider restoring VaVoom plugin because there's k8VaVoom now
DescriptionOver at Doomworld forums there's a thread about k8VaVoom source-port which is a continuation of VaVoom with a new author. Right now this is still a fresh thing, however it may be a reason to reconsider restoring VaVoom plugin to life.
Additional InformationThe thread:'https://www.doomworld.com/forum/topic/102766-k8vavoom-no-good-thing-ever-dies/ [^]'
Attached Files

- Relationships

-  Notes
User avatar (0020140)
Pol M (developer)
2018-10-22 15:04

It sounds interesting. There's definitely some investment put into k8VaVoom, so if it is as easy as renaming VaVoom to k8VaVoom, I'd go for it. Probably mentioning it to the author would be ok? Just in case he plans to change how VaVoom servers work (Assumption done here)

I'll probably also try to make a package for Arch, I like having the possibility of using as all the possible plugins that Doomseeker may or may not have.
User avatar (0020141)
Zalewa (developer)
2018-10-22 15:08

Even though this may be rude to say, I'd hate to have a situation where we revive the plugin only for the author to lose interest in the next few weeks. If port is usable now and stays usable, there will be no harm, but if the port will enter a state of perpetual bugginess then the revival will amount to nothing. I just don't want to jump on the party too early.

I'll PM ketmar about this proposal and wait for response.
User avatar (0020142)
Pol M (developer)
2018-10-22 15:49
edited on: 2018-10-22 16:14

Quote from Zalewa
I'd hate to have a situation where we revive the plugin only for the author to lose interest in the next few weeks. If port is usable now and stays usable, there will be no harm, but if the port will enter a state of perpetual bugginess then the revival will amount to nothing. I just don't want to jump on the party too early.


Completely agrees. 👌

User avatar (0020143)
Zalewa (developer)
2018-10-22 18:58

Ketmar's reply:
Quote from ketmar

hi. let me write a somewhat lengthy response. ;-)

 

first, about my plans. there are no plans to lost interest to k8VaVoom: i am working on it for almost a year already, this is the only sourceport i am using to play DooM, and i am playing DooM at least several hours a week. while there may be pauses in developement for weeks or even monthes, i am not planning to declare EOL over k8VaVoom in the foreseeable future. ;-) if you'll look at commit history, you will see that Doomworld announce wasn't made in a hurry -- there were more than 6 monthes of development before the announce. ;-)

 

that is, have no fear, k8VaVoom is not going to disappear soon.

 

second: thank you for your proposal, adding support for k8VaVoom to Doomseeker will be great! but as ticket says, it is prolly too early to revive [k8]VaVoom support. the network protocol is going to change (including master server protocol). actually it is already incompatible with the original VaVoom, and i am planning to rework networking later. tbh, i don't even know if it works reliably yet. that is, simply renaming the plugin will probably won't work.

 

yet i am ready to talk and cooperate, of course. if you need something special (like special protocol to talk with Doomseeker, so that protocol can be declared "stable", and you won't have to change your code when i change something on my side), i am ready to implement it.

 

thank you for considering k8VaVoom worth supporting, and feel free to quote my message in ticket/contact me if you'll have any questions/ideas/etc. i don't think that i will be able to support k8VaVoom plugin myself, but i am always ready to resolve issues and fix things on my side, if necessary.
User avatar (0020144)
Pol M (developer)
2018-10-22 19:18

Well, I'd say that this concludes it for the moment, at least until Ketmar says the protocol is done.
User avatar (0020145)
Zalewa (developer)
2018-10-22 19:28

Marking this as "resolved - suspended".

Issue Community Support
This issue is already marked as resolved.
If you feel that is not the case, please reopen it and explain why.
Supporters: No one explicitly supports this issue yet.
Opponents: No one explicitly opposes this issue yet.

- Issue History
Date Modified Username Field Change
2018-10-20 06:06 Zalewa New Issue
2018-10-20 09:06 Zalewa Summary Restore VaVoom plugin because there's k8VaVoom now => Consider restoring VaVoom plugin because there's k8VaVoom now
2018-10-20 12:35 WubTheCaptain Status new => acknowledged
2018-10-22 15:04 Pol M Note Added: 0020140
2018-10-22 15:08 Zalewa Note Added: 0020141
2018-10-22 15:49 Pol M Note Added: 0020142
2018-10-22 16:14 Pol M Note Edited: 0020142 View Revisions
2018-10-22 18:58 Zalewa Note Added: 0020143
2018-10-22 19:18 Pol M Note Added: 0020144
2018-10-22 19:28 Zalewa Note Added: 0020145
2018-10-22 19:28 Zalewa Status acknowledged => resolved
2018-10-22 19:28 Zalewa Resolution open => suspended
2018-10-22 19:28 Zalewa Assigned To => Zalewa
2018-10-22 19:28 Zalewa Assigned To Zalewa =>
2018-11-02 09:46 WubTheCaptain Status resolved => closed






Questions or other issues? Contact Us.

Links


Copyright © 2000 - 2025 MantisBT Team
Powered by Mantis Bugtracker