Talk:Coding Needs
From Hero of Allacrost
Same thing for this page too, let's use the Bug Tracker. ~ Gorzuate 22 September 2006
Questions about some editor tasks
First, I guess we prefer using this wiki page rather than the Bug Tracker? Hmm... the bug tracker would seem easier to keep up to date.
Auto-occlusion detection: what do you mean by unviewable tiles? If you mean invalid/non-existing tiles in a tileset that the map designer may unintentionally paint onto the map, then ok, I know how to fix that.
Text editor: is this just a simple text editor? All it can do is edit text, save scripts, load existing scripts, and create new scripts? If so, it seems to me like the user would be more inclined to create/edit scripts in their favorite text editor, rather than by using this simplistic one.
~ Gorzuate 25 April 2007
Its easier to create the entries on this page rather than file each as a separate feature request in the bug tracker. I personally like this page because I can take a quick glance at all of the things our programming team has to do, which would be difficult with the bug tracker. Anyway...
By auto-occlusion detection I mean if I lay down a lower layer tile, and then draw a middle layer or upper layer tile on top of it that is fully opaque, then the lower layer tile will never be seen by the player at all, and thus we shouldn't even be drawing that lower layer tile.
The text editor is just a simple editor, yes. What this editor can do that another text editor can not do is make it easier for the user to define script functions etc. while the editor still has the map open. Its not a good idea to have both the editor and an external text editor both modifying and saving changes to the same file.
--Roots 14:04, 25 April 2007 (PDT)
