Suggestions for the future: Difference between revisions

From EDukeWiki
Jump to navigation Jump to search
→‎Scripting: add "Access to engine-side tables"
Fox (talk | contribs)
No edit summary
Line 2: Line 2:


== Scripting ==
== Scripting ==
Cutscene support - http://forums.duke4.net/topic/2961-paper-cuts-minor-bugs-and-annoyances/page__view__findpost__p__152896<br/>
* 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<br/>
* 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.


== Rendering ==
== Rendering ==


== Other ==
== Other ==

Revision as of 08:49, 29 March 2013

This page is intended to prodive 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

Rendering

Other