Quote from PootisClockwork»
Just use curseforge. Even though it's owned by Twitch, you can still download stuff and search for things alot easier
You misunderstand, I don't download stuff here very often, I am talking about the stuff that I created that other people download. My adventure map for example has about 1600 downloads (Most of which came from this website)
Luigi's Mansion - A Minecraft Adventure Map
1
I have discovered the nature of the bug, and have fixed it in the new 1.6.5.
With the /teleport command, when you are using an entity as your destination, it must only target a single entity in 1.13. 1.12 was a little more casual with this and it just picked one essentially at random. So now the Command Converter will insert sort=nearest,limit=1 at the end of target selectors that need them if they don't already have it.
Also, I've been broiling up some ideas for the future of the Command Converter, but for now, they will be on the back burner.
'Til next time!
0
I can't wait to see what you have created! 3 years stacked up must mean something.
I will continue to work at this World Converter whenever I can, and hopefully it will be able to convert your world's command blocks to 1.13. But just keep in mind that it is highly experimental, and as a prototype in a language that I am unfamiliar with, it may take some time to thoroughly create. But I will give it my best!
Thanks for the inspiration to keep on pushing.
And 'til next time, never cease to amaze!
1
Yes, quite so.
I am still working at that World Converter every now and then; it is one of those new-frontier kinda things if you get my drift. I'll probably have to mess around with Microsoft Visual Studio and make mods/hacked clients as training in Java to produce this World Converter.
0
Thank you for the comment.
I do not know why specifically this has happened to you; could you send some screen shots of the folder layout and the on-screen Command Converter for your option settings and what you type into Input/Output?
I cannot diagnose the problem without information as to what caused the issue.
'Til next time!
0
Thanks for the tip! I will do some research on this and see if I can figure out how to implement this into the Command Converter.
0
After 2 months of no updates and/or bug reports, I finally found a bug...
I was converting a one-command of mine and it had a few problems coming out the other end. I have fixed these bugs with the new 1.6.4!
Now, I did some research into that World Converter that was mentioned a while back, and I came out with some unfortunate discoveries...
I don't believe it is possible without using some sort of third party program to extract the chunk files from the region files, as, when converted to text, the region files are just a mess (much like .zip archives). So there is no way I can use batch alone to extract the data. If anyone has any ideas as to how to do it, I can make the World Converter function like the Folder Converter.
And if it turns out to be possible, I will investigate the Bedrock Converter while I'm at it.
P.S. As of this point in time, the download count is 4742. Honestly, this blew me away when it first exploded. I am deeply honored by this. I thank you all for your interest in my program. Thanks for the good run.
And 'til next time, never cease to amaze!
0
I couldn't find any issues with the command itself, nor anything that would freak out the Command Converter.
One thing that I did spot out was that you converted this with the Lite version...
Here is a quote from Instructions.txt...
"However, the Lite version cannot support files of over 5 KB in size, anything bigger than this should be run through one of the other two."
The Lite version is meant for very small commands. If you try to use a one-command of this size, it will not work properly under the Lite version. Use the normal version to convert this.
That should be all. If something goes wrong after this, just tell me and I will look deeper into this.
P.S. There is no 1.6.4 as of the posting of this comment, it must be a typo intended to say "1.6.3."
'Til next time!
0
Thanks for the bug report. I have discovered the nature of the bug...
It didn't cross my mind while I was originally programming the Command Converter, but "boat" is the only ID shared by an item and an entity. This little detail causes the program to go a little haywire with the NBT data.
Now, of the three (known) ways to specify entity IDs in NBT data (spawn eggs, mob spawners, and the Passengers tag), the Passengers tag is the only one that is practically used with boats (since spawn eggs won't work at all, and mob spawners are just weird with boats). I modified the Command Converter to check to see if it is currently in the location where an entity would be specified under the Passengers tag, if so, it will switch the "oak_boat" from the item conversion to "boat" in the entity conversion.
Hopefully this fixes the bug that you described. And of course, the 1.6.3 contains that which I have just described.
'Til next time!
0
Okay, I have found the bug. You remember when I said that the Modified Volume Mode was rather experimental? Yeah, that is why.
I have modified key areas of the mode and now the trains turn and slope normally.
With commands that were location-sensitive, it would shift the location of execution to the lowest northwest corner of the block. I changed it to execute from the lowest central point of the block. It is impossible for this to work and return it to its source location, but the middle of the block is better than the corner.
Sorry that you have to run everything through again, but if you want this one specifically to go through faster just slap in this:
positioned ~0.5 ~ ~0.5
...whenever you see this:
execute as @e[team=Train,scores={trainturn=1..}] align xyz as @s[dx=0,dy=5,dz=0] run teleport @s ~ ~4 ~
...to turn it into this:
execute as @e[team=Train,scores={trainturn=1..}] align xyz as @s[dx=0,dy=5,dz=0] positioned ~0.5 ~ ~0.5 run teleport @s ~ ~4 ~
NOTE: The only effected functions that I could find were trainturn_trigger(1-8).
There might be more specific places that need this, however. If this alone doesn't solve everything, just run it all through with the new 1.6.2.
And that pretty much wraps things up for now. Based on how things are looking, it seems that these were the final bugs in the train data pack (but I may be wrong).
'Til next time!
0
Could you private message me the data pack that you are currently using? Because I can't really convert large quantities of stuff myself practically, having the version that you're using will aid in debugging. Hopefully it is a simple fix.
0
I ran the commands in question through the 1.6.0, and concerning the commands causing the issues with turning and the cart spawning, it converted perfectly and the trains showed no issue with it. I believe you didn't enable the optional settings to activate these features. They are called "Modified Volume Mode" and "Modified Distance Mode." Make sure that they are set to "Modified."
As for the spawn egg thing, I discovered the issue. Apparently the program only converted the spawn eggs if the damage value was 0, but the damage values were 60 and 120. Now, the 1.6.1 ignores damage values (as it should have before).
As for that command in "main.mcfunction."
scoreboard players tag @a add traineggparticle {SelectedItem:{id:"minecraft:spawn_egg"}}
This is something that there is no easy fix for. Due to the "Flattening," this can't really be converted within a single command, since you can only specify one block/item per command when checking in NBT. Instead, since it is just a single command, just replace "pig_spawn_egg" (the default that the Command Converter just slaps in as kind of a joke) with "bat_spawn_egg" when it is done converting.
Speaking of converting, I apologize, I will (most likely) be unable to convert all of these functions for you. Because my laptop is very small and weak, converting mass quantities of commands is very impractical. But with this new insight and the new update, you shouldn't run into any more problems.
That's all for now.
'Til next time!
0
The 1.6.0 has been released! Sorry it has taken so long, but this is the single largest update to the program yet. I will address each of you and the things that you have found...
The train data pack that you supplied had a few issues in it that caused all of the problems to occur. I have fixed the three issues that I found in the 1.6.0.
The problems involved volume selection in target selectors, distance in target selectors, and the placement of the Count NBT tag.
Volume selection took a huge overhaul. It turns out, in 1.12, volume selection would start at the lowest northwest corner of a block, and look from there. But in 1.13, it starts at the location of execution. This is what caused the problem with the train turning mechanism. The structures that handled turning looked for the train directly above them, but because they used volume detection, the train lied just outside the boundary, so it was undetected, therefore, never turned. With a new optional setting enabled, commands with the volume selection used will adjust their execution location using align to detect everything as it should. However, it certain very specific situations, this new feature may cause some issues, hence it being optional.
Distance in target selectors was a tad weird. Turns out, in 1.13, if you are looking for an entity on the very edge of the distance radius bubble, using a very small distance (like 2), on the negative side of the bubble, it seems to miss it by a hair. At least, this is what I found. By expanding the range of the bubble by one-one-millionth of a block, it detects it no problem. This whole distance thing is what was causing the issue with only one cart being able to be added. This is because the train removes the ability to add more if it is moving, and the cart didn't find the train in front of it, so it began to move. And this caused the issue.
Now the Count placement tag wasn't really a bug, but more of an enhancement. In the areas controlling the wood-filled carts, the Damage tag wasn't detected (because Count was in the way), so the wood was set to oak_planks instead of what they should have been. Since this is very common in commands, I decided to make it cope with it.
Also, I created that Folder Converter that you wanted. It works very well based off of what I have seen.
If you run into any more problems, tell me right away! A lot of this release is slightly experimental. I did do thorough bug testing, but it is nearly impossible to get everything on the first try.
The issue that I found was quite simple compared to the others. It involved the limit argument in target selectors (formally known as c). In 1.12, when limit is used, it automatically searched for the nearest entities within the limit (unless @r was used). And if the number was negative, it searches the furthest. But in 1.13, with the addition of sort, it doesn't add any sorting mechanism into limit upon inclusion. And because the Command Converter didn't include sort=nearest into the commands, when the armor stand tries to teleport itself to the invisible armor stand, it targets the invisible armor stand to teleport to itself. And only when it gets out of range (by teleporting down) is it able to target itself. With the addition of sort=nearest accompanying limit, it no longer jumps as it did before.
I have added Minimized Mode as an optional setting that causes all new windows opened up by the Command Converter to start off minimized. This should solve all of your issues.
This bug took a little research to tackle. But it now converts all of the banner commands correctly, along with some other NBT stuff that I didn't notice until now. I did test this thoroughly in-game, and the banners did come through the correct colors.
But for the record, the Base tag is not supposed to be used in /give commands for items to determine color, the damage value is for that. But for the sake of convenience, if it finds Base in item NBT, it will modify the color regardless of damage value.
This, to most, seems to be impossible. But because command blocks and signs (the only blocks to store commands) are block entities, they are most likely stored in a more organized way. I will look into this, and it will definitely take a long time to develop if I chose to do so.
Now, there were a few other features that I decided to add that I've been meaning to include for a while. Including the NBT enhancements that I referenced earlier, and function name decapitalization.
In 1.13, with the /function command, it can no longer support capitalized characters, so the Command Converter will now automatically decapitalize the names. Of course, it will require some manual renaming of the actual files (perhaps until I (maybe) make the World Converter for command blocks and functions).
Like I said before, this update contains a lot of experimental content, although it was thoroughly tested, there may always be a bug that slipped through.
P.S. The Instructions.txt document has been completely reworked. Might be worth a re-read.
'Til next time!
0
Thank you so much for the bug report!
I am currently implementing this into the 1.6.0, along with all of the other things. Based on how things are going, the 1.6.0 should be released either tonight or sometime tomorrow.
0
Okay, so...
I am currently working on the 1.6.0. It will contain a lot of the stuff spoken here, along with some bug fixes that I have been researching for a while.
It may take a few days for how massive this update is, but it will fix a lot of issues.
It will also contain a feature that was suggested to me by a private messenger, it will be able to convert every file in a specific folder instead of having to convert every single one individually, or at least that's the plan anyway.
Sorry for the lack of explanation and personal address, but my time is a little tight right now. But I will have more time later on after the 1.6.0 is done to explain everything.
'Til next time!
0
I did not know that. I thank you for the information.
I will look into Bedrock Edition when I get the time. It will take some research to get the hang of the different conversions necessary.
Also, I have released the 1.5.7 to fix some bugs revealed to me by a private messenger.
'Til next time!