Currently the network attributes hyper, multiple, and loops must be FALSE for networkLites. In principle, it may be possible to support these with the current data structure. hyper would make use of tibble list columns (as referenced in #2) to allow a vector of tails and heads for each edge. multiple could use an edge id mechanism similar to that in network to allow referencing a particular one of several parallel edges. loops by itself would not require extensive changes, but the existing code would need to be checked for correctness. As in #2 EpiModel runtime needs to be considered when making any generalizations to networkLite. I am not aware of any need for these options in current applications, but wanted to note that in principle they could be supported.