Anonymous | Login | Signup for a new account | 2025-07-28 08:12 UTC | ![]() |
My View | View Issues | Change Log | Roadmap | Zandronum Issue Support Ranking | Rules | My Account |
View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||
0002635 | Zandronum | [All Projects] Suggestion | public | 2016-02-13 20:58 | 2016-03-03 11:55 | ||||
Reporter | Decay | ||||||||
Assigned To | |||||||||
Priority | normal | Severity | tweak | Reproducibility | always | ||||
Status | closed | Resolution | not fixable | ||||||
Platform | Microsoft | OS | Windows | OS Version | XP/Vista/7 | ||||
Product Version | 2.1 | ||||||||
Target Version | Fixed in Version | ||||||||
Summary | 0002635: R_DrawPlayerSprites | ||||||||
Description | R_DrawPlayerSprites True When set to false, the players weapon that is displayed on HUD will be hidden and not rendered. Essentially players can make their weapons disappear for maximum visibility, most notable in maps with large height differences when freelook is disabled, aka most OS servers. While everyone can do it, I feel it should be a server-regulated flag. | ||||||||
Steps To Reproduce | step 1 execute zandronum step 2 open console step 3 type in r_drawplayersprites 0 | ||||||||
Attached Files | ![]() | ||||||||
![]() |
|
Dusk (developer) 2016-02-22 19:08 |
As Leonard demonstrated with his attached WAD, this could be very easily circumvented with sprite replacements, which would severely hamper the effectiveness of such a flag. Is this really what is desired? |
Ch0wW (reporter) 2016-02-27 12:49 edited on: 2016-02-27 12:52 |
I won't give favor for this feature, and even go to strongly reject that BS. In this case, we shouldn't disable movebob as it's not intended by the game? We could also say we must have the classic doom hud as removing it gives more visibility on the screen? (and it's the case) Other fast-fps ports (such as ezQuake) should remove the possibility to set the opacity of their weapons, because it's not intended? Honestly Decay, NO. In this case, play on DOOM2.EXE if you're unhappy :) I'm always up for customization settings, the way "a future of doom" should be, especially if you want to add competitive features to suit everyone. Because, if you want to remove that feature, maybe we will do the same for removing parts of commands that makes auto-SR50 possible, since it gives such an advantage over regular players, don't you think? ;) Also, enfoncing this serverside is not needed (like the health/armor not visible, but not the ammo). Much checks that will be useless for 99% of the people, and ruins more competitive elements. And I won't lie, but I'm modifying my client to enable opacity for the weapons by myself. |
FascistCat (reporter) 2016-02-28 01:23 |
I'm having doubts about having it regulated server-side (though for competitive events should be ok) but why could not we regular players have the desire to do it clientside? I mean, not every player has the ability to edit clients/DECORATE to make their weapons see-through. |
StrikerMan780 (reporter) 2016-02-29 20:16 |
Kind of needed for clean screenshots, so... I'm on the fence about this. |
Decay (reporter) 2016-03-01 20:56 |
>Leonard's attached wad Yes thank you for attaching a wad without explaining it at all, very good. >Chow being very upset and comparing it to other games/ports. Yea but this isn't another game now is it? >Remove other automated commands/movebob/"adding competitive features" I'd be quite happy to see all that automated go/be regulated. As far as I'm concerned, you and many other players use these things to get every edge you can possibly get, and if you are lacking confidence in your skills without these things, that's not my problem 8), I don't mind using the default settings for almost everything. But if you're going to be implementing OS flags to emulate OS, there is no point in doing it if it's just going to be cherry picking. The best argument you might have is the HUD business. But then again, the HUD options are in the menu, not a command input through console. *shrugs* >FascistCat Uhhhh yea anyone can do it that's the point. Did you even read the ticket? >I need clean screenshots Shots of what? Is this really that hard to grasp? I mean this isn't really that big of a deal, but if you're breaking the intent of vertical maps with no freelook (harder see opponent below), maybe it is a problem. |
Leonard (developer) 2016-03-02 12:51 |
Quote from 'Decay' This is exactly why I didn't want to post in this ticket to begin with: your disgusting behavior. To be honest here, the reason the staff didn't decide to masterban you is BEYOND me. Quote from 'Decay' Other than your ass, what are you pulling this out of, might I ask? Quote from 'Decay' Which was exactly the point of the attached wad. Why bother limiting this CVar when you can do the exact same thing just by making wads. |
Ru5tK1ng (updater) 2016-03-02 21:37 |
This isn't the forums, keep your drama out of here or don't add any notes at all. All of you. |
Catastrophe (reporter) 2016-03-03 04:14 edited on: 2016-03-03 04:22 |
Tbh, all you'd have to do on a custom client is uncomment the line that checks if the weaponhide flag is on/off to make this feature rendered null. It's literally zero-effort for anyone that has worked with Zandronum's source to circumvent this. Heck, you wouldn't even need to edit the source, you can already accomplish this by going into wads and replacing weapon sprites. Sure, implementing this feature makes it more inconvenient for people to hide weapons, but does it actually prevent the problem? No. Hypothetically if this were to be implemented, how would we be able to check that someone is hiding their weapon when they shouldn't be? There's just too many assumptions you'd have to make. tl;dr Too easy to circumvent. |
Decay (reporter) 2016-03-03 05:00 |
>Leonard being extremely upset. r o f l >Blue's response. Thank you for this more comprehensive answer. I suppose there's nothing to be done about it, so could probably consider this request rejected/grayed out. |
Dusk (developer) 2016-03-03 11:55 |
Yeah I'm with Catastrophe on this one. People could get around it way too easily. |
This issue is already marked as resolved. If you feel that is not the case, please reopen it and explain why. |
|
Supporters: | Decay Combinebobnt Argentum FascistCat |
Opponents: | capodecima Ch0wW JC Leonard carpathia |
![]() |
|||
Date Modified | Username | Field | Change |
2016-02-13 20:58 | Decay | New Issue | |
2016-02-13 21:00 | Ru5tK1ng | Steps to Reproduce Updated | View Revisions |
2016-02-16 09:06 | capodecima | Note Added: 0014450 | |
2016-02-16 09:06 | capodecima | Note Deleted: 0014450 | |
2016-02-16 09:27 | WaTaKiD | Additional Information Updated | View Revisions |
2016-02-16 13:43 | Leonard | File Added: transweaps.pk3 | |
2016-02-22 19:08 | Dusk | Note Added: 0014477 | |
2016-02-22 19:09 | Dusk | Status | new => feedback |
2016-02-27 12:49 | Ch0wW | Note Added: 0014505 | |
2016-02-27 12:51 | Ch0wW | Note Edited: 0014505 | View Revisions |
2016-02-27 12:52 | Ch0wW | Note Edited: 0014505 | View Revisions |
2016-02-28 01:23 | FascistCat | Note Added: 0014509 | |
2016-02-29 20:16 | StrikerMan780 | Note Added: 0014518 | |
2016-03-01 20:56 | Decay | Note Added: 0014522 | |
2016-03-01 20:56 | Decay | Status | feedback => new |
2016-03-02 12:51 | Leonard | Note Added: 0014534 | |
2016-03-02 21:37 | Ru5tK1ng | Note Added: 0014535 | |
2016-03-03 04:14 | Catastrophe | Note Added: 0014536 | |
2016-03-03 04:17 | Catastrophe | Note Edited: 0014536 | View Revisions |
2016-03-03 04:19 | Catastrophe | Note Edited: 0014536 | View Revisions |
2016-03-03 04:22 | Catastrophe | Note Edited: 0014536 | View Revisions |
2016-03-03 04:22 | Catastrophe | Note Edited: 0014536 | View Revisions |
2016-03-03 05:00 | Decay | Note Added: 0014537 | |
2016-03-03 11:55 | Dusk | Note Added: 0014538 | |
2016-03-03 11:55 | Dusk | Status | new => closed |
2016-03-03 11:55 | Dusk | Resolution | open => not fixable |
Copyright © 2000 - 2025 MantisBT Team |