Suggestions for the future: Difference between revisions
Jump to navigation
Jump to search
Hendricks266 (talk | contribs) mNo edit summary |
No edit summary |
||
| Line 6: | Line 6: | ||
* Creating a palette / lookup table after an image file, similar to tilefromtexture | * Creating a palette / lookup table after an image file, similar to tilefromtexture | ||
* A starttrack-style command that can stop a track, or play the title screen or briefing tracks. | * A starttrack-style command that can stop a track, or play the title screen or briefing tracks. | ||
* EVENT_CHEAT that returns the | * EVENT_CHEAT that returns the ID of an entered cheat. | ||
== Rendering == | == Rendering == | ||
== Other == | == Other == | ||
Revision as of 23:18, 29 March 2013
This page is intended to provide a list of EDuke32 (not Mapster32) suggestions of features that are moderately or highly complex and thus are not expected to be implemented immediately. Feel free to edit this list, but keep the following format: A leading line with a short description, and a link to a post at the Duke4.net forums.
Scripting
- Cutscene support - http://forums.duke4.net/topic/2961-paper-cuts-minor-bugs-and-annoyances/page__view__findpost__p__152896
- Access to engine-side tables (e.g. base palette, translucency) - http://forums.duke4.net/topic/775-eduke32-20-and-polymer/page__view__findpost__p__152969
- Creating a palette / lookup table after an image file, similar to tilefromtexture
- A starttrack-style command that can stop a track, or play the title screen or briefing tracks.
- EVENT_CHEAT that returns the ID of an entered cheat.