-
Notifications
You must be signed in to change notification settings - Fork 61
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
[ENHANCEMENT] Make vehicle entities get an unique entity name. #1707
Comments
Can it be assumed what you actually want is a command to summon vehicles, not them having a unique name specificall? |
Sorry for not responding. |
They will not have unique names. IV registers vehicles as a single entity. Their JSON defines what they do. So no, you just get the basic names. |
So is the /summon command possible at least?
…On Mon, Aug 28, 2023, 3:36 AM DonBruce64 ***@***.***> wrote:
They will not have unique names. IV registers vehicles as a single entity.
Their JSON defines what they do. So no, you just get the basic names.
—
Reply to this email directly, view it on GitHub
<#1707 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ASAVN5X347I2VLSFADTHQ43XXPRYXANCNFSM6AAAAAA3YE7VME>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
If you use the right NBT, yes, you can summon a vehicle now. You don't need anything special for that. |
So whats the right NBG? How do we know what to put in in?
…On Tue, Aug 29, 2023, 12:33 AM DonBruce64 ***@***.***> wrote:
If you use the right NBT, yes, you can summon a vehicle now. You don't
need anything special for that.
—
Reply to this email directly, view it on GitHub
<#1707 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ASAVN5W7KYKRGT6ZLXOM32TXXUFBHANCNFSM6AAAAAA3YE7VME>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
I honestly have no clue. I don't mess with summon commands with NBT normally. Would ask one of the folks who is on servers regularly that do. |
So i'd have to do some research
…On Wed, Aug 30, 2023, 5:58 AM DonBruce64 ***@***.***> wrote:
I honestly have no clue. I don't mess with summon commands with NBT
normally. Would ask one of the folks who is on servers regularly that do.
—
Reply to this email directly, view it on GitHub
<#1707 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ASAVN5S4QJ547OG2JPQ4AH3XX2T5DANCNFSM6AAAAAA3YE7VME>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Right now every MTS vehicles have an entity Identifier name that goes like this:
entity.mts_entity.name(on 1.12.2) and
mts.builder.existing(on 1.16.5).
You can kill the vehicles by running: {"/kill @e[type=mts.builder.existing]"} but you can't summon them, because running "/summon mts.builder.existing" brings up an invisible fake entity.
What i want and i'm sure more people are looking toward this feature is to be able to identify each vehicle by the name of their item: mts:packid.name
ex.
Item name: mts:warkvehicle.containerhandler
entity name: mts:warkvehicle.containerhandler
I believe this would help servers in a big way. They could setup minigames, Races, Roleplays and so much more.
The text was updated successfully, but these errors were encountered: