Halo Custom Edition: Difference between revisions
→Limitations
| Line 34: | Line 34: | ||
===Limitations=== | ===Limitations=== | ||
The engine has become frustrating to many map developers, as more complicated features require more complicated procedures. Theoretically, everything possible with the Halo 2/3 engine is also possible with Halo CE, but is often imperfect. Mappers allow boosting through continuous damage indicators, usually behind the player, to speed up the vehicle. This has been modified to deal 0 damage, but still shows arrows indicating damage on the HUD. There are also possibilities of dual-wielding, although still imperfect. The user converts it into one weapon, replacing the secondary trigger(grenades) for the secondary weapon trigger, although when you pick it up, you instantly pick up two instead of one. One of the most frustrating was the limited space for tags, one of the problems the Custom Mapping Team has faced. This has not been a concern to many mappers, though. | The engine has become frustrating to many map developers, as more complicated features require more complicated procedures. Theoretically, everything possible with the Halo 2/3 engine is also possible with Halo CE, but is often imperfect. Mappers allow boosting through continuous damage indicators, usually behind the player, to speed up the vehicle. This has been modified to deal 0 damage, but still shows arrows indicating damage on the HUD. There are also possibilities of dual-wielding, although still imperfect. The user converts it into one weapon, replacing the secondary trigger(grenades) for the secondary weapon trigger, although when you pick it up, you instantly pick up two instead of one. One of the most frustrating was the limited space for tags, one of the problems the Custom Mapping Team has faced. This has not been a concern to many mappers, though. | ||
==Community== | ==Community== | ||