Griatch

Fixed.

Thanks for the write-up. :) We'll see in the future if this is anything we'll pursue or not.

There are a lot of variations to objects that would make it less than trivial to do this in a general sense. Also, copying _partial_ database content over (especially as...

What you want is creating the game in the database and then export that into a text file that you can move to the other environment to import directly in...

@davewiththenicehat No, dbrefs should hopefully be consistent unless you really mess up your database (Evennia deliberately doesn't reuse dbrefs). The common confusion/bugs usually appear in changes to objects/attributes and relations...

Sure, if you work with dbrefs explicitly in your batchcmd/batchcode file, then you obviously can't expect them to match when moving to another database. But using explicit dbrefs was never...

@Keda87, @vaibhavsingh97 That's great! I updated the issue with some more info. :)

I also added some exceptions. No need to dig into making unit tests for the game_template since it's basically well, empty template files.

@keda87 It's not necessary to run `coverage` locally for this issue. But if you want to try it you need to follow these steps: 1. In your virtualenv, do `pip...

@gulasnani As you can see in TestCommand, the `args` you pass in is stored on the command object here https://github.com/evennia/evennia/blob/master/evennia/commands/default/tests.py#L64. Normally (when a real command is run in Evennia), these...