• Please note: In an effort to ensure that all of our users feel welcome on our forums, we’ve updated our forum rules. You can review the updated rules here: http://forums.wolflair.com/showthread.php?t=5528.

    If a fellow Community member is not following the forum rules, please report the post by clicking the Report button (the red yield sign on the left) located on every post. This will notify the moderators directly. If you have any questions about these new rules, please contact support@wolflair.com.

    - The Lone Wolf Development Team

Alias Collisions

M

MaxSupernova

Well-known member
When I create a topic for "Bolo the Hutt", I also create an alias "Bolo" because I want to have links appear even when I don't list his full name.

Now, when I enter "Bolo the Hutt" in another topic, I get a collision warning because both "Bolo" and "Bolo the Hutt" are possible links.

However, it's a nonsensical collision because one is just a link to the other.

It's a bit of a strange thing to deal with (which words do I want to be a link?) but some logic that determines if both elements in the collision are the same topic (via aliases) and just links the main topic rather than the alias (or the longer of the two or whatever) would be helpful.

I understand that if "Bob" and "Bob Smith" are two separate topics then the collision alerts is necessary, but when they are aliases of the same topic then it's far less relevant.

Does this make sense?

Not a critical improvement, just an annoyance that I ran into.
 
Last edited:
A possible difference is if you pick "Bolo", the engine might continue and offer "Hutt" as a link to the Hutt race entry. Compare to Paranoia where "Mutant Power" is something characters have and "Power" is the stat you roll for using one. Maybe not the best examples, but it's something you have to allow for.
 
Last edited:
Warning about those conflicts are fine, Parody, but when the only conflicts are to the SAME topic, then it shouldn't really indicate a conflict (and always take the longest of the available options).
 
This has already been identified as a bug that we'll be fixing in an upcoming release. So there's no further need to +1 this request . :)
 
You must log in or register to reply here.
Back
Top