Toolset Ideas and Suggestions

[slowdive]

The Beta phase will only be focusing on bug fixing, polishing, polishing and more polishing. This is the place to post ideas and suggestions for post-release tasks.

[youngneil1]

It would be very helpful if placed instances of creatures and props would also display NameWithNotes and CategoryName of the blueprint they belong to (when clicking the info button in the toolset, displayed then in the property window for the instance of this creature/prop). I use both of these heavily for identifying what is what.

[youngneil1]

Playing around with the cool new variable lists right now .

For locals it might be helpful to display the name of the prop/creature/whatever they're on first. Right now I have many entries of the very same local variable without me being able to see from which object exactly it comes.

[slowdive]

[sidermaniac]

[slowdive]

Some good ideas there sidermaniac. I'll add them to the list. About the module installer, the only thing players need to do is copy the module folder to the "IceBlink v1xx\modules" folder. That's it. If the module author is telling people to move graphic files around, that is an older issue we had, but is no longer valid. The engine searches almost everywhere for images so you shouldn't have to copy files anywhere. We/I need to make sure and have a good document on where module authors should place files in the module's folders for consistency (but the engine does search in lots of places just in case).

[sidermaniac]

[sinopip]

It would be good to be able to zoom in and out on a area display, to help design medium to large areas.

[sinopip]

I used a map of 47x44 (that's 3008x2816px) and remembered it needed to be a power of 2 when I started a new game (crash). I extended the canvas size with IrfanView to 4096x4096px, putting the image in the canvas at the top left, and found that the map walkable tiles were screwed up.

It would be good to have a warning message when an map image is loaded and not a power of 2.

! Edit : map size should be no more than 2048x2048px. It must be an engine limitation as it gives me outofmemory error when running the engine on a bigger map.

[slowdive]

Ahh, yes I need to have a warning about power of 2 for all graphic resources. The maximum size of a map is dependent on the graphic cards memory so it is best to stay under 2048 x 2048 just to be sure it'll work on everyone's PC.