Anonymous | Login | Signup for a new account | 2024-04-25 12:50 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 | ||||||||
0001324 | Zandronum | [All Projects] Suggestion | public | 2013-04-15 02:44 | 2014-06-13 17:58 | ||||||||
Reporter | HexaDoken | ||||||||||||
Assigned To | |||||||||||||
Priority | normal | Severity | feature | Reproducibility | N/A | ||||||||
Status | feedback | Resolution | open | ||||||||||
Platform | OS | OS Version | |||||||||||
Product Version | 1.0 | ||||||||||||
Target Version | Fixed in Version | ||||||||||||
Summary | 0001324: Warn about sprite conflicts on startup | ||||||||||||
Description | When you create mods and fill in custom sprites, there is that little chance that some of the sprite names you think on the fly happen to be identical to other sprite names that exist in your IWAD or other PWADs you load alongside. This can cause problems such as objects going invisible or having a completely inapporitate sprite. And this is very bad. To make matters worse, unless you remember all sprite names by heart(you don't), it's very hard to spot such things. What I suggest is to make an option that, when enabled, makes zandronum give out console warnings each time it encounters a sprite conflict, similar to how it gives out warnings for each actor conflict. So at least you can check out the console and go all "oh shit I derped". Why this should be an option? Because there are mods that actually rely on the behaviour of sprite replacement - loading up such mods would result in your console getting flooded by warnings, which are in fact intended behaviour. That is why average users probably want it off. But if you are a mod-maker, and you are making a mod where you want to avoid sprite conflicts, this feature would be infinitely useful. Just make it in a CVar, or, if CVars are ignored on startup, a command line parameter. | ||||||||||||
Attached Files | |||||||||||||
Notes | |
(0006285) Konar6 (reporter) 2013-04-15 08:03 |
This could be added to existing sv_showwarnings. |
(0009233) Watermelon (developer) 2014-06-13 17:57 edited on: 2014-06-13 17:58 |
Should this be in zdoom first? Not that I have a problem doing this ticket |
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. |
Issue History | |||
Date Modified | Username | Field | Change |
2013-04-15 02:44 | HexaDoken | New Issue | |
2013-04-15 08:03 | Konar6 | Note Added: 0006285 | |
2014-06-13 17:57 | Watermelon | Note Added: 0009233 | |
2014-06-13 17:57 | Watermelon | Status | new => feedback |
2014-06-13 17:58 | Watermelon | Note Edited: 0009233 | View Revisions |
Copyright © 2000 - 2024 MantisBT Team |