Using /home in the twilight teleports you to the twilight portal still on the twilight side. When you go through the portal and then use /home again it says there isn't a home point set up or something like that.
Actually, I think it bugged if you set a home point before the twilight portal was created. It's not bugging anymore
Thank you. The visual made it very clear. that is good.
I know what the problem is. I have misunderstood part of the code. It was supposed to display that ONLY when the /help ta was called. but it is doing it for every thing /help. This is my mistake. I plan to fix this within 2 days. I have to code around my real life issues.
I just finished making the update for mc version 1.7.10 and will make the final jar file soon. Then I will make the same changes for mc v1.8 then release a new version SpawnCommands Teleport officially. I have not yet released any of these changes but they are in hand.
1. fixed the /help disaster. oops! I had misunderstood the forge code and now its working properly, not interfering with every usage of /help.
2. fixed the /ta (Teleport Ask) to not require exact capitalization of player names. /ta LarryBoy will be the same as /ta larryboy now. Basically it corrects your capitalization for you.
3. fixed the problem with invisible blocks such as Railcraft:residual.heat blocks interfering with teleporting. BUT you may still need to add that block name to the SpawnCommands config file for blocks that can be spawned into. You may also need to redefine your malfunctioning named spawn locations once.
Any new worlds will have this block name included in the default configuration. The symptoms were when you teleport you jump in the air before landing and you sometimes land on top of the tree or building or mountain you are supposed to be arriving under. oops. This was an interaction between this mod and and an invisible block from Railcraft.
Remember that this is not yet released but will be very soon.
Thought you all might like an update.
-Andre
[EDIT:]
4. I also made the list of your spawn locations clickable in the chat window. Clicking on a location name will be the same effect as typing the command to go there. Example: You type /spawns and the list of your named locations is displayed in chat. You then hit "t" to bring up chat again and then click on a name in that list. Poof! You are teleported there.
5. Twilight Forest bed location is odd. I made Spawn Commands ignore any bed location defined in Twilight Forest. Aparently the Twilight Forest mod sets a bed location for you next to a portal into that world. Now if you type /spawn. to go back to your bed it will try to send you to the main overworld bed location instead.
6. Made the /spawn? display include the local dimension bed location, if there is any. Your player location, main world spawn location, and main overworld bed location, are still displayed as usual. Aparently Minecraft supports bed locations in different dimensions. It does seem to require that the world be a "Surface World" to sleep in a bed. SpawnCommands /spawn. and /home will send you to your main overworld bed location if no local bed location is set.
I am running JUST MC 1.8.0 with Forge 1421 (and all other versions back to recommended) and JUST your mod.
If you do /sethome it works fine to do /home from anywhere.
BUT, once you place a bed and you sleep there, /home lands you 10-16 blocks below the bed if done from more than 256 blocks away.
I have tested low and high Y heights, short and long teleports, both night and day, in creative or survival mode, and can say without a doubt it happens every the time.
It can be 'fixed' with a simple /sethome beside the bed after you sleep, but sure is a pain, because you have to do it every time.
I am running JUST MC 1.8.0 with Forge 1421 (and all other versions back to recommended) and JUST your mod.
If you do /sethome it works fine to do /home from anywhere.
BUT, once you place a bed and you sleep there, /home lands you 10-16 blocks below the bed if done from more than 256 blocks away.
I have tested low and high Y heights, short and long teleports, both night and day, in creative or survival mode, and can say without a doubt it happens every the time.
It can be 'fixed' with a simple /sethome beside the bed after you sleep, but sure is a pain, because you have to do it every time.
This is a known problem and would love to know any solution to it. Your testing is very much appreciated in full by me. I have also tested this but not in the exact same way as you so far.
In the past I have concluded that there is no code or function difference between respawning from death and typing /home with this mod. Also that the minecraft transports the player to the location before loading the chunk for that location. It then within a small amount of time will let you appear to fall then put you back where you should be, normally. BUT if it takes longer than usual to load the chunks in that area you actually do fall before it assembles the world around you. This encases you in stone or what ever is below where you were supposed to be. This is dark and suffocates you to death again. This leads me to believe it is a design flaw in the core minecraft code that did not account for slow load times. This has been my test results so far.
I am mildly hopeful that you may have uncovered a solution.
"if done from more than 256 blocks away" This is consistant with my testing and the load time theory.
"10-16 blocks below" This is what I experienced to but more like up to 5 below when I tested it.
Setting the bed location with /sethome or /spawn! then being able to teleport to there with /home or /spawn. from any distance is encouraging but I suspect that your client or server had the chunks loaded on both ends already making a speedy load time. Not sure, just guessing.
"It can be 'fixed' with" setting the /home beside the bed. THIS is what gives me some good thoughts on fixing this. The only difference I see between the exact head of the bed location being the bed coordinates and a spot beside the bed is the idea that, just maybe, arriving at the real bed location puts you inside the head of the bed block which is not air but the one beside lands you in the air but standing on (not in) a block. THIS is worth looking into. This is purely guessing and I have not looked into the minecraft code on this.
I will say that 99.9% of the time a medium range or short range teleport to the bed works perfectly leaving the player standing in the head of the bead just fine and able to walk away normally.
I am running JUST MC 1.8.0 with Forge 1421 (and all other versions back to recommended) and JUST your mod.
If you do /sethome it works fine to do /home from anywhere.
BUT, once you place a bed and you sleep there, /home lands you 10-16 blocks below the bed if done from more than 256 blocks away.
I have tested low and high Y heights, short and long teleports, both night and day, in creative or survival mode, and can say without a doubt it happens every the time.
It can be 'fixed' with a simple /sethome beside the bed after you sleep, but sure is a pain, because you have to do it every time.
This is a known problem and would love to know any solution to it. Your testing is very much appreciated in full by me. I have also tested this but not in the exact same way as you so far.
In the past I have concluded that there is no code or function difference between respawning from death and typing /home with this mod. Also that the minecraft transports the player to the location before loading the chunk for that location. It then within a small amount of time will let you appear to fall then put you back where you should be, normally. BUT if it takes longer than usual to load the chunks in that area you actually do fall before it assembles the world around you. This encases you in stone or what ever is below where you were supposed to be. This is dark and suffocates you to death again. This leads me to believe it is a design flaw in the core minecraft code that did not account for slow load times. This has been my test results so far.
I am mildly hopeful that you may have uncovered a solution.
"if done from more than 256 blocks away" This is consistant with my testing and the load time theory.
"10-16 blocks below" This is what I experienced to but more like up to 5 below when I tested it.
Setting the bed location with /sethome or /spawn! then being able to teleport to there with /home or /spawn. from any distance is encouraging but I suspect that your client or server had the chunks loaded on both ends already making a speedy load time. Not sure, just guessing.
"It can be 'fixed' with" setting the /sethome beside the bed? THIS is what gives me some good thoughts on fixing this. The only difference I see between the exact head of the bed location being the bed coordinates and a spot beside the bed is the idea that, just maybe, arriving at the real bed location puts you inside the head of the bed block which is not air, but the one beside lands you in the air but standing on (not in) a block. THIS is worth looking into. This is purely guessing and I have not looked into the minecraft code on this.
I will say that 99.9% of the time a medium range or short range teleport to the bed works perfectly leaving the player standing in the head of the bead just fine and able to walk away normally.
Thank you for your research =)
--Andre
ps: I suppose I could check for the presence of the bed at the exact bed location and search for an open spot beside it or just above it then reset the bed location to there. If you marked your bed location by sleeping in it then the coordinates are set by minecraft to the head of the bed. If you die after that it does seem to place you beside it. I can put the check into my code to go to the bed and do it similarly. =) I might try this. It certainly would not make things worse. Thanks again.
Awesome, glad to help! (if even just s little bit) I didn't understand why, but actually, after your description it makes total sense now. When you sleep, your head location is technically In the Bed, because it moves your viewpoint down.
Vanilla Teleport 'assumes' your feet is the block below your head.
Maybe add /home+ that puts you one or two blocks above?
We really do love your mod, as it makes life easier for my players.
I am also going to ask for one new feature:
/stuck which teleports you ~ ~1 ~
as it is also a known bug that sometimes you end up "in" blocks less than one tall, like carpet, and cant't move.
The only 'solution' right now is to jump a lot and Hope for the best or to log out and back in. At night this could mean dying to mobs.
/stuck as conceived above would allow you to "pop up above it" after local loading.
Awesome, glad to help! (if even just s little bit) I didn't understand why, but actually, after your description it makes total sense now. When you sleep, your head location is technically In the Bed, because it moves your viewpoint down.
Vanilla Teleport 'assumes' your feet is the block below your head.
Maybe add /home+ that puts you one or two blocks above?
We really do love your mod, as it makes life easier for my players.
I am also going to ask for one new feature:
/stuck which teleports you ~ ~1 ~
as it is also a known bug that sometimes you end up "in" blocks less than one tall, like carpet, and cant't move.
The only 'solution' right now is to jump a lot and Hope for the best or to log out and back in. At night this could mean dying to mobs.
/stuck as conceived above would allow you to "pop up above it" after local loading.
Would this be possible? and would you add it?
Thanks for the positive feedback. Its really nice to get some.
New feature request/stuck
It will be easy to code but what exactly would it do? I mean precisely.
Ive been stuck and had to jump many times so a teleport searching for an open spot up a block or 3 sure. But Ive been stuck and the only really out was sideways as well. So I am asking what exactly should the /stuck do so as to not allow it to be abused. I could see someone walking up to someone elses wall and typing /stuck and bam they are standing on the overhang up on the wall. hmmm. lol ideas please.
I am about to release a new version of SpawnCommands Teleport with bug fixes and some small upgrades. If we do this quickly I could include it in this update.
Speaking of updates the idea for stopping the falling by placing the bed location beside the bedis now implimented in the new release thats almost done. What it does is when you go to your bed location it checks for a bed in that exact spot. If it finds a bed block there it attempts to move the bed location next to the bed instead. It actually searches around the head of the bed on every side within 1 block for an open location and IF it does find an open location it changes your bed/home location to right there but leaves the bed physically where it is. If it cannot find an open location it continues with no change. I hope this actually does fix or even reduces the falling below the bed problem.
Technical note about your comment "Vanilla Teleport 'assumes' your feet is the block below your head." Minecraft has a very specific coordinate for your player at any given time. It is at the bottom of your feet. Effects such as the view from sleeping are probably just a rendered effect and most likely your character is actually set to the coordinates of the block that is the head of the bed. Thats my understanding.
Interesting info about it looking at your feet all the time, didn't know that!
I still think it places your head at the bed level.
IF so, that would explain the clipping, because it would be placing your feet in the block below the bed.
Maybe, like all things Mojang, this is one of the 'exceptions' where they allow you to be in a solid object and use some code to keep you in place?
Ok, for /stuck I didn't think it through and you are right, it would be situational.
So;
how about "/stuck [direction]" N,S,E,W,U,D ?
It would allow you to teleport only one space in a given direction
and only allow you to do it once every X seconds (15 seconds? to avoid people using it as a wall bypass)
Also, maybe a keybind for it?
That way any teleport into an object would be quickly 'fixed' but you couldn't teleport abuse.
ALSO, couldn't /home and your bed sleep spawn point be Different points? Right now it's only an issue because sleeping in the bed overwrites your /sethome
(maybe actually disable the whole bed sleeping changing spawn point routine?)
OFFICIAL RELEASE of SpawnCommands Teleportversion 2.2.0 for Minecraft 1.7.10 and Minecraft 1.8.
This includes several bug fixes and the ability to click on the names of your locations displayed by /spawns. Also the Teleport Ask command (similar to tpa) now does not need to have the exact capitalization of the player name.
Yea! finally.
Please notify me of any issues as soon as you can. Thank you.
OFFICIAL RELEASE of SpawnCommands Teleportversion 2.2.0 for Minecraft 1.7.10 and Minecraft 1.8.
This includes several bug fixes and the ability to click on the names of your locations displayed by /spawns. Also the Teleport Ask command (similar to tpa) now does not need to have the exact capitalization of the player name.
Yea! finally.
Please notify me of any issues as soon as you can. Thank you.
Awesome thanx ! I love the additions of being able to click on the destination name and spawning beside my bed on home.
The Meaning of Life, the Universe, and Everything.
Join Date:
4/3/2013
Posts:
49
Member Details
I haven't been able to get it working properly in my Forge 1.8 server. It worked for a bit at first but then kept giving an error saying it couldn't save the file correctly when /spawn was used.
Rollback Post to RevisionRollBack
Corruption resides within us all.
I do not restrain my corruption so my mind is free.
I am the true me.
I haven't been able to get it working properly in my Forge 1.8 server. It worked for a bit at first but then kept giving an error saying it couldn't save the file correctly when /spawn was used.
If you have it client side, it will cause issues on SMP servers. Remove from client side and things should work.
If you have it client side, it will cause issues on SMP servers. Remove from client side and things should work.
Nope, I'm the server owner and I actually have a mod blocker so no one could join with it clientside. Nothing worked properly, I think I fixed it by changing the "enable if cheats disabled" from false to true. /spawn seems to work, haven't tested the other ones. /ta worked for a bit but now it says players aren't online when they are so the tele request can't be sent.
btw andrenoel, everyone's confused about /ta, they're used to /tpa. xD
Nope, I'm the server owner and I actually have a mod blocker so no one could join with it clientside. Nothing worked properly, I think I fixed it by changing the "enable if cheats disabled" from false to true. /spawn seems to work, haven't tested the other ones. /ta worked for a bit but now it says players aren't online when they are so the tele request can't be sent.
btw andrenoel, everyone's confused about /ta, they're used to /tpa. xD
1. What exact version of Spawn Commands are you using on your server? I hope its version 2.2.0 or up. The player not online thing was due to it requiring the exact capitalization of the user name and is now changed to be case insensative thankfully.
2. Yes I know. I believe the way /ta is setup now is very efficient and it makes sense to me. I really hope it makes sense to others. So far it seems an improvement over /tpa or so I hope. Please do give suggestions for the help page for it or for any aspect of it if you wish.
On this last note: when I have been using /ta recently the scenario generally goes like this:
1. I type /ta friennamehere in lower case or even just type /ta, a space, then i hit tab a few times to find the player name. I then hit enter ofcourse.
2. my friend will type /ta ok. I get notified in chat that they have accepted.
3. then I just hit either t or slash to open chat then I usually hit up arrow once to bring up my last command which is usually my /ta friendname request and hit enter.
4. bam im there.
This is how I have used it efficiently recently. (today actually)
im trying to keep it simple and very very usable. Thoughts about its design are welcome.
Is it just the change of how to do it or is there something about the way /ta is designed that is making it uncomfortable to use?
Yup, that did the trick!
Thanks so much!
Seems like /sethome gets reset if you try to use /home in the twilight
i will test it. thanks.
also if you leave twilight forest does it then work again?
my published mods
Using /home in the twilight teleports you to the twilight portal still on the twilight side. When you go through the portal and then use /home again it says there isn't a home point set up or something like that.
Actually, I think it bugged if you set a home point before the twilight portal was created. It's not bugging anymore
Bug Report, no error messages in console of client or server in regards to it.
When I type /help in game your help for the spawn commands appears at the top of each page and effectively destroys the remaining help pages.
https://www.mediafire.com/folder/40mie1v6ame54/SpawnCommands_Teleport
Thank you. The visual made it very clear. that is good.
I know what the problem is. I have misunderstood part of the code. It was supposed to display that ONLY when the /help ta was called. but it is doing it for every thing /help. This is my mistake. I plan to fix this within 2 days. I have to code around my real life issues.
my published mods
cool
I just finished making the update for mc version 1.7.10 and will make the final jar file soon. Then I will make the same changes for mc v1.8 then release a new version SpawnCommands Teleport officially. I have not yet released any of these changes but they are in hand.
1. fixed the /help disaster. oops! I had misunderstood the forge code and now its working properly, not interfering with every usage of /help.
2. fixed the /ta (Teleport Ask) to not require exact capitalization of player names. /ta LarryBoy will be the same as /ta larryboy now. Basically it corrects your capitalization for you.
3. fixed the problem with invisible blocks such as Railcraft:residual.heat blocks interfering with teleporting. BUT you may still need to add that block name to the SpawnCommands config file for blocks that can be spawned into. You may also need to redefine your malfunctioning named spawn locations once.
Any new worlds will have this block name included in the default configuration. The symptoms were when you teleport you jump in the air before landing and you sometimes land on top of the tree or building or mountain you are supposed to be arriving under. oops. This was an interaction between this mod and and an invisible block from Railcraft.
Remember that this is not yet released but will be very soon.
Thought you all might like an update.
-Andre
[EDIT:]
4. I also made the list of your spawn locations clickable in the chat window. Clicking on a location name will be the same effect as typing the command to go there. Example: You type /spawns and the list of your named locations is displayed in chat. You then hit "t" to bring up chat again and then click on a name in that list. Poof! You are teleported there.
5. Twilight Forest bed location is odd. I made Spawn Commands ignore any bed location defined in Twilight Forest. Aparently the Twilight Forest mod sets a bed location for you next to a portal into that world. Now if you type /spawn. to go back to your bed it will try to send you to the main overworld bed location instead.
6. Made the /spawn? display include the local dimension bed location, if there is any. Your player location, main world spawn location, and main overworld bed location, are still displayed as usual. Aparently Minecraft supports bed locations in different dimensions. It does seem to require that the world be a "Surface World" to sleep in a bed. SpawnCommands /spawn. and /home will send you to your main overworld bed location if no local bed location is set.
my published mods
I am running JUST MC 1.8.0 with Forge 1421 (and all other versions back to recommended) and JUST your mod.
If you do /sethome it works fine to do /home from anywhere.
BUT, once you place a bed and you sleep there, /home lands you 10-16 blocks below the bed if done from more than 256 blocks away.
I have tested low and high Y heights, short and long teleports, both night and day, in creative or survival mode, and can say without a doubt it happens every the time.
It can be 'fixed' with a simple /sethome beside the bed after you sleep, but sure is a pain, because you have to do it every time.
-Grimm
see also :
http://www.minecraftforum.net/forums/mapping-and-modding/minecraft-mods/2131444-1-8-or-1-7-10-or-1-7-2-or-1-6-4-forge?comment=77
http://www.minecraftforum.net/forums/mapping-and-modding/minecraft-mods/2131444-1-8-or-1-7-10-or-1-7-2-or-1-6-4-forge?comment=83
This is a known problem and would love to know any solution to it. Your testing is very much appreciated in full by me. I have also tested this but not in the exact same way as you so far.
In the past I have concluded that there is no code or function difference between respawning from death and typing /home with this mod. Also that the minecraft transports the player to the location before loading the chunk for that location. It then within a small amount of time will let you appear to fall then put you back where you should be, normally. BUT if it takes longer than usual to load the chunks in that area you actually do fall before it assembles the world around you. This encases you in stone or what ever is below where you were supposed to be. This is dark and suffocates you to death again. This leads me to believe it is a design flaw in the core minecraft code that did not account for slow load times. This has been my test results so far.
I am mildly hopeful that you may have uncovered a solution.
"if done from more than 256 blocks away" This is consistant with my testing and the load time theory.
"10-16 blocks below" This is what I experienced to but more like up to 5 below when I tested it.
Setting the bed location with /sethome or /spawn! then being able to teleport to there with /home or /spawn. from any distance is encouraging but I suspect that your client or server had the chunks loaded on both ends already making a speedy load time. Not sure, just guessing.
"It can be 'fixed' with" setting the /home beside the bed. THIS is what gives me some good thoughts on fixing this. The only difference I see between the exact head of the bed location being the bed coordinates and a spot beside the bed is the idea that, just maybe, arriving at the real bed location puts you inside the head of the bed block which is not air but the one beside lands you in the air but standing on (not in) a block. THIS is worth looking into. This is purely guessing and I have not looked into the minecraft code on this.
I will say that 99.9% of the time a medium range or short range teleport to the bed works perfectly leaving the player standing in the head of the bead just fine and able to walk away normally.
Thank you for your research =)
--Andre
my published mods
see also :
http://www.minecraftforum.net/forums/mapping-and-modding/minecraft-mods/2131444-1-8-or-1-7-10-or-1-7-2-or-1-6-4-forge?comment=77
http://www.minecraftforum.net/forums/mapping-and-modding/minecraft-mods/2131444-1-8-or-1-7-10-or-1-7-2-or-1-6-4-forge?comment=83
This is a known problem and would love to know any solution to it. Your testing is very much appreciated in full by me. I have also tested this but not in the exact same way as you so far.
In the past I have concluded that there is no code or function difference between respawning from death and typing /home with this mod. Also that the minecraft transports the player to the location before loading the chunk for that location. It then within a small amount of time will let you appear to fall then put you back where you should be, normally. BUT if it takes longer than usual to load the chunks in that area you actually do fall before it assembles the world around you. This encases you in stone or what ever is below where you were supposed to be. This is dark and suffocates you to death again. This leads me to believe it is a design flaw in the core minecraft code that did not account for slow load times. This has been my test results so far.
I am mildly hopeful that you may have uncovered a solution.
"if done from more than 256 blocks away" This is consistant with my testing and the load time theory.
"10-16 blocks below" This is what I experienced to but more like up to 5 below when I tested it.
Setting the bed location with /sethome or /spawn! then being able to teleport to there with /home or /spawn. from any distance is encouraging but I suspect that your client or server had the chunks loaded on both ends already making a speedy load time. Not sure, just guessing.
"It can be 'fixed' with" setting the /sethome beside the bed? THIS is what gives me some good thoughts on fixing this. The only difference I see between the exact head of the bed location being the bed coordinates and a spot beside the bed is the idea that, just maybe, arriving at the real bed location puts you inside the head of the bed block which is not air, but the one beside lands you in the air but standing on (not in) a block. THIS is worth looking into. This is purely guessing and I have not looked into the minecraft code on this.
I will say that 99.9% of the time a medium range or short range teleport to the bed works perfectly leaving the player standing in the head of the bead just fine and able to walk away normally.
Thank you for your research =)
--Andre
ps: I suppose I could check for the presence of the bed at the exact bed location and search for an open spot beside it or just above it then reset the bed location to there. If you marked your bed location by sleeping in it then the coordinates are set by minecraft to the head of the bed. If you die after that it does seem to place you beside it. I can put the check into my code to go to the bed and do it similarly. =) I might try this. It certainly would not make things worse. Thanks again.
my published mods
Awesome, glad to help! (if even just s little bit) I didn't understand why, but actually, after your description it makes total sense now. When you sleep, your head location is technically In the Bed, because it moves your viewpoint down.
Vanilla Teleport 'assumes' your feet is the block below your head.
Maybe add /home+ that puts you one or two blocks above?
We really do love your mod, as it makes life easier for my players.
I am also going to ask for one new feature:
/stuck which teleports you ~ ~1 ~
as it is also a known bug that sometimes you end up "in" blocks less than one tall, like carpet, and cant't move.
The only 'solution' right now is to jump a lot and Hope for the best or to log out and back in. At night this could mean dying to mobs.
/stuck as conceived above would allow you to "pop up above it" after local loading.
Would this be possible? and would you add it?
[quote=grimmliberty;../../../members/grimmliberty;2131444-1-8-or-1-7-10-or-1-7-2-or-1-6-4-forge?comment=97]
Awesome, glad to help! (if even just s little bit) I didn't understand why, but actually, after your description it makes total sense now. When you sleep, your head location is technically In the Bed, because it moves your viewpoint down.
Vanilla Teleport 'assumes' your feet is the block below your head.
Maybe add /home+ that puts you one or two blocks above?
We really do love your mod, as it makes life easier for my players.
I am also going to ask for one new feature:
/stuck which teleports you ~ ~1 ~
as it is also a known bug that sometimes you end up "in" blocks less than one tall, like carpet, and cant't move.
The only 'solution' right now is to jump a lot and Hope for the best or to log out and back in. At night this could mean dying to mobs.
/stuck as conceived above would allow you to "pop up above it" after local loading.
Would this be possible? and would you add it?
Thanks for the positive feedback. Its really nice to get some.
New feature request /stuck
It will be easy to code but what exactly would it do? I mean precisely.
Ive been stuck and had to jump many times so a teleport searching for an open spot up a block or 3 sure. But Ive been stuck and the only really out was sideways as well. So I am asking what exactly should the /stuck do so as to not allow it to be abused. I could see someone walking up to someone elses wall and typing /stuck and bam they are standing on the overhang up on the wall. hmmm. lol ideas please.
I am about to release a new version of SpawnCommands Teleport with bug fixes and some small upgrades. If we do this quickly I could include it in this update.
Speaking of updates the idea for stopping the falling by placing the bed location beside the bed is now implimented in the new release thats almost done. What it does is when you go to your bed location it checks for a bed in that exact spot. If it finds a bed block there it attempts to move the bed location next to the bed instead. It actually searches around the head of the bed on every side within 1 block for an open location and IF it does find an open location it changes your bed/home location to right there but leaves the bed physically where it is. If it cannot find an open location it continues with no change. I hope this actually does fix or even reduces the falling below the bed problem.
Technical note about your comment "Vanilla Teleport 'assumes' your feet is the block below your head." Minecraft has a very specific coordinate for your player at any given time. It is at the bottom of your feet. Effects such as the view from sleeping are probably just a rendered effect and most likely your character is actually set to the coordinates of the block that is the head of the bed. Thats my understanding.
my published mods
Interesting info about it looking at your feet all the time, didn't know that!
I still think it places your head at the bed level.
IF so, that would explain the clipping, because it would be placing your feet in the block below the bed.
Maybe, like all things Mojang, this is one of the 'exceptions' where they allow you to be in a solid object and use some code to keep you in place?
Ok, for /stuck I didn't think it through and you are right, it would be situational.
So;
how about "/stuck [direction]" N,S,E,W,U,D ?
It would allow you to teleport only one space in a given direction
and only allow you to do it once every X seconds (15 seconds? to avoid people using it as a wall bypass)
Also, maybe a keybind for it?
That way any teleport into an object would be quickly 'fixed' but you couldn't teleport abuse.
ALSO, couldn't /home and your bed sleep spawn point be Different points? Right now it's only an issue because sleeping in the bed overwrites your /sethome
(maybe actually disable the whole bed sleeping changing spawn point routine?)
OFFICIAL RELEASE of SpawnCommands Teleport version 2.2.0 for Minecraft 1.7.10 and Minecraft 1.8.
This includes several bug fixes and the ability to click on the names of your locations displayed by /spawns. Also the Teleport Ask command (similar to tpa) now does not need to have the exact capitalization of the player name.
Yea! finally.
Please notify me of any issues as soon as you can. Thank you.
my published mods
Awesome thanx ! I love the additions of being able to click on the destination name and spawning beside my bed on home.
Great work , thank you
I haven't been able to get it working properly in my Forge 1.8 server. It worked for a bit at first but then kept giving an error saying it couldn't save the file correctly when /spawn was used.
I do not restrain my corruption so my mind is free.
I am the true me.
If you have it client side, it will cause issues on SMP servers. Remove from client side and things should work.
Nope, I'm the server owner and I actually have a mod blocker so no one could join with it clientside. Nothing worked properly, I think I fixed it by changing the "enable if cheats disabled" from false to true. /spawn seems to work, haven't tested the other ones. /ta worked for a bit but now it says players aren't online when they are so the tele request can't be sent.
btw andrenoel, everyone's confused about /ta, they're used to /tpa. xD
I do not restrain my corruption so my mind is free.
I am the true me.
1. What exact version of Spawn Commands are you using on your server? I hope its version 2.2.0 or up. The player not online thing was due to it requiring the exact capitalization of the user name and is now changed to be case insensative thankfully.
2. Yes I know. I believe the way /ta is setup now is very efficient and it makes sense to me. I really hope it makes sense to others. So far it seems an improvement over /tpa or so I hope. Please do give suggestions for the help page for it or for any aspect of it if you wish.
On this last note: when I have been using /ta recently the scenario generally goes like this:
1. I type /ta friennamehere in lower case or even just type /ta, a space, then i hit tab a few times to find the player name. I then hit enter ofcourse.
2. my friend will type /ta ok. I get notified in chat that they have accepted.
3. then I just hit either t or slash to open chat then I usually hit up arrow once to bring up my last command which is usually my /ta friendname request and hit enter.
4. bam im there.
This is how I have used it efficiently recently. (today actually)
im trying to keep it simple and very very usable. Thoughts about its design are welcome.
Is it just the change of how to do it or is there something about the way /ta is designed that is making it uncomfortable to use?
my published mods