shanish reports: To use Entity detector to dete ... #1517
Labels
No Label
1. kind/balancing
1. kind/breaking
1. kind/bug
1. kind/construction
1. kind/documentation
1. kind/enhancement
1. kind/griefing
1. kind/invalid
1. kind/meme
1. kind/node limit
1. kind/other
1. kind/protocol
2. prio/controversial
2. prio/critical
2. prio/elevated
2. prio/good first issue
2. prio/interesting
2. prio/low
3. source/art
3. source/client
3. source/engine
3. source/ingame
3. source/integration
3. source/lag
3. source/license
3. source/mod upstream
3. source/unknown
3. source/website
4. step/approved
4. step/at work
4. step/blocked
4. step/discussion
4. step/help wanted
4. step/needs confirmation
4. step/partially fixed
4. step/question
4. step/ready to deploy
4. step/ready to QA test
4. step/want approval
5. result/cannot reproduce
5. result/duplicate
5. result/fixed
5. result/maybe
5. result/wontfix
ugh/petz
ugh/QA main
ugh/QA NOK
ugh/QA OK
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#1517
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
shanish reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
Teleport command:
Compass command:
entities don't have IDs the same way that nodes do, it only matters when they are initialized
and petz decided to use different values for the name of the entity, and the name of the item used to spawn them (vs. e.g. how mobs_redo does it)
With this command we can find all objects near a player and send the entitystrings to them.
Maybe the zoo should have entity strings, since the entity detector needs those?
so, i was mostly wrong about there not being a reliable way to get the entity string - usually,
object.get_luaentity().name
will have the value you want.the entity detector could be set up w/ an api to "alias" certain names, so that either the egg itemstring or the entity itemstring would work.
Kind of like entity_string is a "technical" name and the entity detector also accepts "trivial names", like "pony"?
There is no way one egg name can result in different entities?
Or we could introduce a Zookeeper NPC who looks at the players inventory and sends them a mail which entity-strings come out of the eggs they have in store.
there certainly could be, though i don't know if there are any in practice.
either way, this is a low-priority thing for me, but it'd be nice to solve it eventually.