Maniaplanet Forum

Thanks for reporting the crash. I've fixed it.
I've also added the shortcuts as requested.

Same download link.

Wow, you're so fast
Btw, thanks for the shortcuts

Well Im having trouble with Dirt. After I resave the track and open them the dirt gets removed? got any ideas? Perhaps a dropped down list of all the blocks?

This tool is great, thanks!
Looks like there went quite some work into it.

Some (I hope) minor suggestions:
- add a reload option
- remember the directory of the last edited map when clicking "Open..."
- make it so that the "Flags" field is displayed and can be edited in hexadecimal instead of decimal (that is because this part is logically structured that way, for example setting the fifth hexadecimal digit to 1 changes a block to the version of it that is attached to the ground (this applies for Stadium at least))
- (optional) enumerate the block list (ideally skipping unassigned blocks)
- (very optional) add wildcard searching (so you can e.g. type "<12,_,17> to search for all blocks with x=12, z=17)

xt3 wrote:Also I found Y 9 the height Of the block to be Y 1 onChallengeEdit.

TGYoshi wrote:I'm not entirely sure what your issue is with the block Y coordinate, I'm not completely understanding you.

I'm also not sure what xt3's issue is, but I guess what he is pointing at is that the ground level in Stadium used to be at y=1 in ChallengeEdit/TMF, as opposed to y=9 in MapEdit/MP. I'm pretty sure though that this is not a bug in the tool, but rather a difference between the old Stadium and the new. After all, in all TM envis other than Stadium you could always have tunnels below ground level, so it's perfectly normal to have y>1 for that level. This change is most probably due to the addition of the new tunnel blocks shown at the ManiaGala.

TGYoshi wrote: I do not recommend editing unassigned blocks tho, unless you edit the block above to a non-linked block.
You can use the Clone button to copy a block and edit it that way. It could help.

Could you shed some light on this "unassigned blocks" business? What are they for? Why do you get crashes when removing them? What is a non-linked block, is this like the "primary" blocks in ChallengeEdit (the ones marked "P")?

xt3 wrote:Well Im having trouble with Dirt. After I resave the track and open them the dirt gets removed? got any ideas? Perhaps a dropped down list of all the blocks?

I have the same troubles. But again i guess that this is a MP-issue and not a MapEdit one. When you load a map, the editor runs some routine which checks all blocks and adds some Clips etc. It seems that this routine makes blockmixed terrain blocks vanish. Maybe Tiggs knows more about this.

I have done some testing, and this seems to suggest that the terrain blocks remain intact if you do not edit the map ingame after saving it in MapEdit (validating and calculating shadows seems to be ok though). So a fix seems to be to postpone any terrain editing work until the very end of the building process.

Of course this is not really satisfactory, so if no other solution can be found, it could be nice to add a feature to MapEdit which lets you save a list of blocks in a seperate file (much like the macro blocks of the ingame editor) and to add such lists of blocks to the end of a map file. That way you could save your blockmixed terrain blocks and restore them whenever they get killed by the game.

paul13 wrote:

TGYoshi wrote: I do not recommend editing unassigned blocks tho, unless you edit the block above to a non-linked block.
You can use the Clone button to copy a block and edit it that way. It could help.

Could you shed some light on this "unassigned blocks" business? What are they for? Why do you get crashes when removing them? What is a non-linked block, is this like the "primary" blocks in ChallengeEdit (the ones marked "P")?

So true I found one that I removed for an imported track. If I mixed a block around I wouldn't be able to open it but when I removed said block it raised all of the track up by 8. So One things the unnassaigned does is hold them down I guess.

paul13 wrote:

xt3 wrote:Well Im having trouble with Dirt. After I resave the track and open them the dirt gets removed? got any ideas? Perhaps a dropped down list of all the blocks?

I have the same troubles. But again i guess that this is a MP-issue and not a MapEdit one. When you load a map, the editor runs some routine which checks all blocks and adds some Clips etc. It seems that this routine makes blockmixed terrain blocks vanish. Maybe Tiggs knows more about this.
[/quote]
true! although if I edit the dirt, from a past track from united it will remove most but some will stay that is in the air. These pieces are mixed dirt in the air. Some dirt stays the same on y9 the new Y1. I also found that any dirt mixing at Y8 stays in place and I have mixed water under them so it looks like a lake.

I've updated the application.

paul13 wrote:...

I've added a reload option, the directory is now saved at both save and load, the thing next to flags is now displayed in hexadecimal as binary is too tedious. Changing the input to hexadecimal requires a custom widget which takes more time to code. Might do that later.
Bulk editing will come soonâ„¢ (select multiple blocks, edit them all at the same time) with a translate movement thing as well (select a whole set of blocks, translate by +5 on X etc.).
Regex searching might come later as Boost's regex lib requires me to build it.

I can not be entirely sure about Unassigned blocks, but I'm relatively sure that it always refers to the block above it.
Linked blocks (includes terrain) always seem to have unassigned blocks below them. As a result you have to clone this Unassigned block as well, if you clone e.g. a terrain block.
They are for sure not related to primary blocks in ChallengeEdit. MapEdit loads and saves the map in a different way, which, as a result, eliminates the "primary" blocks (they are actually lookback string definitions).

About terrain, this is caused by how the Maniaplanet editor [SAVES] your map (Loading goes fine). My ideas about terrain follow; Flat, default terrain will not be saved (so in Stadium grass). In this screenshot ( http://i.imgur.com/QaUcqlf.jpg ) the left terrain will save correctly, even though it's modified, but the right one will not save and turn into grass. This will both save: http://i.imgur.com/suJjgFP.jpg .

interesting.

TGYoshi wrote: I can not be entirely sure about Unassigned blocks, but I'm relatively sure that it always refers to the block above it.
Linked blocks (includes terrain) always seem to have unassigned blocks below them. As a result you have to clone this Unassigned block as well, if you clone e.g. a terrain block.
They are for sure not related to primary blocks in ChallengeEdit. MapEdit loads and saves the map in a different way, which, as a result, eliminates the "primary" blocks (they are actually lookback string definitions).

About terrain, this is caused by how the Maniaplanet editor [SAVES] your map (Loading goes fine). My ideas about terrain follow; Flat, default terrain will not be saved (so in Stadium grass). In this screenshot ( http://i.imgur.com/QaUcqlf.jpg ) the left terrain will save correctly, even though it's modified, but the right one will not save and turn into grass. This will both save: http://i.imgur.com/suJjgFP.jpg .

Interesting. The unassigned. perhaps we can create them. That way we can have said dirt blocks stay. Ill look at it

cool and great sharing
thanks

For the next release, I recommend an undo/redo option and a multi selection in order to change coordinates for several blocks.

Good work!

Multiselection is coming, but I've got my hands on some other things at the moment.
Undo and redo might come, not sure if it's really needed once multiselection works .