Guidelines

Respect /r/Linux_Gaming as a community. It's a place for discussing GNU/Linux gaming and GNU/Linux games. 'Discussion' is the key there; if what you want to post (whether image, video, text or other) is more of a monologue than the start of a dialogue, then you're probably in the wrong place.

Respect other users. Disagreement is fine, unwarranted insults are not.

Help others learn as others helped us learn. Sometimes this will mean simply directing users to more suitable places to ask their questions and that's fine, that's helping.

Both debs and rpms are just common archive files with some metadata. There's nothing mysterious or special about them. You can extract the files inside a deb in any distro using ar, and the same goes for rpm (use rpmextract).

The problem is not the package format, but maybe missing libraries (or more commonly, missing specific versions of libraries) the game executable might require to work. But they also can be installed. This might require more or less work depending of the distro, but it's always possible.

Steam games are not made for any package format, they install trough steam digital distribution

Steam it self is 2 part on linux, client and runtime.
Client is... well, client and steam-runtime consists of distro independent libraries. Game which is run trough steam doesn't even use system libraries, but rather those from steam-runtime. This is why it shouldn't really matter which distro you run for steam

yea, and if you go with korora as i suggested here you have few useful pointers (don't worry, it is the same fedora, only difference is what you end up with after installation, all installs/updates are from official fedora repository)

All Linux distributions use package managers to achieve similiar goals. The files are ultimately the same (there may be some small differences where they go), it's just the package managers that are different.

To use a windows analogue, an .MSI-based installer is a framework of package management for Windows, it's just a standard for putting the files and setting configurations, and the windows installer framework manages the format.

Back before all of this, on Linux you had to build everything from source (download the source files and compile it) and install it yourself; you can still do this if you attempt a Linux From Scratch (LFS) build (a common school project). This, of course, is difficult and time consuming. People wrote programs to manage this automatically and from this several standards emerged.

Steam on Linux is effectively a meta-package manager for the Valve system, both on Linux and Windows. It brings its own Linux libraries (even if you have them on your system), and looks after the game storage and library linking at game runtime.

They recommend a .deb based system (specifically Ubuntu) because that's what they tested it on. In reality the communities and developers of these projects converted the .deb installer almost immediately.

Multilib is 32/64 bit. When you see that word it means distro is providing both sets which can live at the same time and applications will use which ever set they need, as far as your question I answered it when in other thread ;)