Developer Blogs
This is a blog for all the cool, but minor, things that your creators do for you.
[ Am | Council | Cwc | Developers | Fluffos | Forn | General | Guilds | Klatch | Learning | Liaison | Mudlib | Playerkillers | Playtesters | Quiz | Ram | Special | Sur | Underworld | Waterways | Web ]
| A Fine Disregard For Awkward Facts, posted on Fri May 30 12:39:34 2025 | | Posted by: Kake | | Category: General | A bug has been identified that was sometimes letting objects be put inside containers when they shouldn't have fitted due to length and width restrictions. This bug has been in place for a long time, so we wanted to give you all a heads-up before we fix it, so you can adjust your inventories, aliases, routines, etc as appropriate.
As a first step, we have added code that will give a WARNING when you try to put something inside a container it shouldn't fit into; but for now, the over-large thing will still agree to go inside the container.
When we put in the full fix, the warning will be removed and the over-large thing will no longer agree to go inside the container. This will happen no sooner than two weeks from the date of this blog post, i.e. you have at least two weeks to check your items and find alternative containers where necessary. But please don't leave it until the last minute!
What you should do:
(a) If you have any items that you aren't definitely 100% sure are small enough to correctly fit inside the containers you regularly store them in, test them by taking them out of the containers and putting them back in again. If no warning is printed, you should be fine.
(b) If item A going into item B is super-important to you, test them anyway even if you're definitely 100% sure it will correctly fit.
(c) If an item gives you a warning and you don't think it should (i.e. you are sure that the length of the container is at least as big as the length of the item, and the width of the container is at least as big as the width of the item), make two bug reps: one on the item and one on the container. This is an EXCEPTION to our normal rule of avoiding duplicate bug reps - we want a rep on each object so we know exactly what you were testing with. |
| Archives |
Subscribe to this blog through RSS
Back to
list of blogs.
