-
-
Notifications
You must be signed in to change notification settings - Fork 685
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Plural aliasing fails to match in stacked/quiet searches #3432
Comments
Looks like the objects I suspect it's only called on the first rock normally (the others are stacked with it so they are not treated as individual objects). That's why there's only one return in the I'm reluctant to always create these aliases for all objects on-creation, but unless we device some other, more programmatic way to query for plural forms, it's probably what needs to happen. 🤔 |
Yeah, I puzzled over how exactly to write up this issue for a while because of exactly that. But I think at the moment the expectation of how it should work is probably to add the plural aliases to everything, mostly because of the docstring for evennia/evennia/objects/objects.py Lines 1447 to 1448 in 0593144
|
An alternative here is to maybe expand the But maybe it could be a special case ... then there would be no need for an explicit alias (at least not for this use case). Then again, english plural forms are not always easy to generalize 😅 |
Describe the bug
Something in the way Evennia adds plural aliases to objects, or possibly the way it searches for them, is breaking search results and only returning one match, even when
stacked
orquiet
are set.To Reproduce
Steps to reproduce the behavior:
Create 3 items named "rock" in your location and then enter the following py lines
Expected behavior
If the auto-generated alias "rocks" is expected to be usable at all, it should match exactly the same search results as the regular key "rock".
Environment, Evennia version, OS etc
evennia 3.1.1
The text was updated successfully, but these errors were encountered: