I think Epic said they wanted to move away from the idea of UE being a fps engine. This means that you can do more and different things than with UDK, but you will have to do everything yourself (unless it’s any of the basic stuff in the example games).
As for blueprints, you don’t need to do anything in it, you can do everything in c++ if you want to, some people just find blueprints easier to use. I think most of the classes that you are missing are very specific, and shouldn’t be too hard to recreate in UE4 (jump pads have already been added to the UT project created by a (non-epic) developer).