Describe the bug

Minor bug involving passing a set as a kwarg to the msg method-- the set is correctly identified as an iterable, but is then presumed to be subscriptable in subsequent operations.

https://github.com/evennia/evennia/blob/574d7fbd4f65cae60c534fe592803057d452ed7b/evennia/server/sessionhandler.py#L252-L262

This does not work on set objects.

self.msg(locks=se

Brief summary of issue / Description of requested feature:

We have one usage of Q_FOREACH. This had been discouraged for some time (since 2016-06-16).
https://github.com/Mudlet/Mudlet/blob/c5285d17615029a7af245948f7dad18c8c39fecc/src/Host.cpp#L1785

Steps to reproduce the issue / Reasons for adding feature:

1. Look at Qt documentation within Qt Creator:

`Q_FOREACH(variable, co

What is the current behavior?

When you are on top of an NPC and want to trade/shop/bank with them. The popup screen will not popup UNTIL you move and FINISH its progress.

**If the current behavior is a bug, please provide

Switch games from belongs_to :user to has_many :admins

Create a new join table that let's multiple users administrate a game. No special roles at the moment, all admins can manage the full aspect of a game.

Maybe we keep the current belongs_to :user and rename to be the "owner" so we can tell who originally made it and maybe who should have slight extra power in the future. Other syst

web client - allow client-side CSS. People like to customize, let them upload or supply their own CSS?

In the Item class (found in the Item folder of the GameLogic project)

1. Add a new enum value to ItemTypes called Money
2. Add a property of type int called Value to Item.cs this is to store the value of the money.

With a money item in the room, assuming it's called Gold coin

1. The user will see "(500) gold coins stacked here."
   • 500 comes from the value property of th

Problems like #235 keep popping up and while the new version does fix the reason those values become None, even if they did become None again in the future, that should not cause a panic.
A simple message to the user that the version check failed should be sufficient - the rest of Blightmud can continue without issue.

I suggest going over every unwrap and expect in the code and thinkin