Page cover image

🏯Legion

You can buy the map on tebex.

How to install the map ?

  • For load map, just ensure molo_legionsquare or molo_legionsquare_sewer on server.cfg and restart server.

  • Make sure you don't make a subfolder.

  • If you use winscp or filezilla please verify that the file.fxap is sent successfully.

  • If you had a problem with the mapping, maybe try uploading again, sometimes ftp can break files.

If you use Pillbox and Legion Square

If you use Mrpd and Legion Square

If you use Sewers and Legion Square

If you use Sewers | Legion Square | Mrpd | Pillbox

The map disappears ?

If you have a problem like this, it is a conflict with a around map.

So it is not a problem with the map.

To fix this problem, you need to find which map is causing the problem.

Then, you are redirected to this tutorial.

If you don't know how to do it even with the tutorials, please use Vertex Hub Compatibility Tool.

Floating props

If you have a problem like this, it is a conflict with a around map.

So it is not a problem with the map.

To fix this problem, you need to find which map is causing the problem.

Then, you are redirected to this tutorial.

If you don't know how to do it even with the tutorials, please use Vertex Hub Compatibility Tool.

Floating lights

If you have a problem like this, it is a conflict with a around map.

So it is not a problem with the map.

To fix this problem, you need to find which map is causing the problem.

Then, you are redirected to this tutorial.

If you don't know how to do it even with the tutorials, please use Vertex Hub Compatibility Tool.

Change textures (logo, color etc)

If you want to change the textures of this mapping, you can look at its files.

molo_legionlod_txt.ytd

molo_legion_txd.ytd

molo_legion2_txd.ytd

If you don't know how to change textures, please watch the tutorial here.

You can't enter of mlo ?

If you can't enter the mlo or walk the entire melo, you have a collision conflict. (.ybn)

Conflict

  • If you encounter conflicts with other mappings, check if you have this in other mappings with a simple search, and remove duplicates in other mappings, then check if you have a problem with the other mapping in question .

  • vw_distlodlights_medium015.ymap

  • vw_distlodlights_medium019.ymap

  • vw_distlodlights_medium022.ymap

  • vw_distlodlights_small029.ymap

  • vw_distlodlights_small037.ymap

  • vw_distlodlights_small046.ymap

  • vw_lodlights_medium015.ymap

  • vw_lodlights_medium019.ymap

  • vw_lodlights_medium022.ymap

  • vw_lodlights_small029.ymap

  • vw_lodlights_small037.ymap

  • vw_lodlights_small046.ymap

  • hi@dt1_13_0.ybn

  • hi@dt1_18_0.ybn

  • hi@dt1_rd1_9.ybn

  • ma@dt1_13_0.ybn

  • dt1_13_0.ybn

  • dt1_18_0.ybn

  • dt1_rd1_3.ybn

  • dt1_rd1_4.ybn

  • hei_dt1_occl_04.ymap

  • hei_dt1_occl_05.ymap

  • dt1_occl_04.ymap

  • dt1_occl_05.ymap

  • ba_barriers_case1.ymap

  • ba_case1_dixon.ymap

  • ba_case1_forsale.ymap

  • ba_case1_madonna.ymap

  • ba_case1_solomun.ymap

  • ba_case1_taleofus.ymap

  • ba_mpbattleipl_long_0.ymap

  • ba_mpbattleipl_strm_0.ymap

  • hei_dt1_13.ymap

  • hei_dt1_13_strm_0.ymap

  • hei_dt1_18.ymap

  • hei_dt1_18_strm_0.ymap

  • hei_dt1_lod.ymap

  • hei_dt1_rd1.ymap

  • hei_dt1_rd1_critical_1.ymap

  • hei_dt1_rd1_long_1.ymap

  • hei_dt1_rd1_strm_5.ymap

  • hei_dt1_rd1_strm_6.ymap

  • dt1_13.ymap

  • dt1_13_strm_0.ymap

  • dt1_18.ymap

  • dt1_18_strm_0.ymap

  • dt1_lod.ymap

  • dt1_rd1.ymap

  • dt1_rd1_critical_1.ymap

  • dt1_rd1_long_1.ymap

  • dt1_rd1_strm_5.ymap

  • dt1_rd1_strm_6.ymap

  • prop_dt1_13_groundlight.ydr

  • prop_dt1_13_walllightsource.ydr

  • dt1_13_build1.ydr

  • dt1_13_build2.ydr

  • dt1_13_dt_13_ems.ydr

  • dt1_13_dtlb.ydr

  • dt1_13_fountainwater.ydr

  • dt1_13_fur1.ydr

  • dt1_13_fur2.ydr

  • dt1_13_fur7.ydr

  • dt1_13_fur8.ydr

  • dt1_13_grounddetaila.ydr

  • dt1_13_grounddetailb.ydr

  • dt1_13_superlod_children.ydd

  • dt1_18_build_roof.ydr

  • dt1_18_build0.ydr

  • dt1_18_build1.ydr

  • dt1_18_build2.ydr

  • dt1_18_build2_detail.ydr

  • dt1_18_build3.ydr

  • dt1_18_build4.ydr

  • dt1_18_build4_em.ydr

  • dt1_18_build4_em_lod.ydr

Position

x= 159.9631652832, y= -1034.7875976563, z= 29.189506530762

Last updated