From 44e1c4a644ed53124a75b443e70dd2e3889a35a8 Mon Sep 17 00:00:00 2001 From: Jason Jones Date: Tue, 11 Dec 2018 12:23:09 -0900 Subject: [PATCH] Use overmapbuffer.place_special in debug special placement This brings debug placement more in line with the placement done during map generation, e.g. it will make connections, record placement into the data structure tying overmap terrains to the special that placed them, and so on. --- src/overmap_ui.cpp | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/src/overmap_ui.cpp b/src/overmap_ui.cpp index 5f4b66424d8f8..e5e0b167c7bc2 100644 --- a/src/overmap_ui.cpp +++ b/src/overmap_ui.cpp @@ -1151,10 +1151,9 @@ tripoint display( const tripoint &orig, const draw_data_t &data = draw_data_t() overmap_buffer.ter( curs ) = uistate.place_terrain->id.id(); overmap_buffer.set_seen( curs.x, curs.y, curs.z, true ); } else { + overmap_buffer.place_special( *uistate.place_special, curs, uistate.omedit_rotation, false, true ); for( const auto &s_ter : uistate.place_special->terrains ) { const tripoint pos = curs + om_direction::rotate( s_ter.p, uistate.omedit_rotation ); - - overmap_buffer.ter( pos ) = s_ter.terrain->get_rotated( uistate.omedit_rotation ); overmap_buffer.set_seen( pos.x, pos.y, pos.z, true ); } }