Can you please share the minimums steps to reproduce the bug?
4 Likes
- Have a package with several R15 characters in it, including humanoids
- Publish your place
- Open your place
- The package thinks something has changed and won’t let you revert the package or publish the place until you publish the package
That said, it can be as little as one R15 humanoid.
3 Likes
I cannot reproduce this on my end. Is this 100% reproducible on your end? Can you provide a screen recording for it? Thanks!
4 Likes
Sure. Basically I just open a place where I have packages with humanoids in them, and it thinks they’ve changed. Reverting the package to a “previous” state also doesn’t solve it.
A package that experiences it if it helps:
https://www.roblox.com/library/3189985193/SentryUnit
I see this same issue frequently, and it it makes packages very untrustworthy.
My solution is to practice good modeling hygiene (however these I can’t prove any of these work).
- When I position packages, don’t place them where they intersect with other Objects.
- I resize items in packages to whole number increments, rather than by dragging to arbitrary decimal numbers.
Also, and more importantly. I use disposable “dummy” copies of my packages in my game layout, and then my code swaps these out for the real package. This way, I can disconnect the dummy from the package, and it doesn’t matter if it gets corrupted.
3 Likes
Very interesting ideas for how to work around this bug, I appreciate the insight.
- I would guess intersecting packages with objects would likely cause the system to think it’s changed. Regardless, this practice is something I always do, but for some reason I still experience it.
- Sadly sticking to whole numbers isn’t always feasible - especially for R15 NPCs. I’ve done this for non-NPC packages and it works fairly well though. Back before some of the fixes, moving/rotating a package on a decimal scale could end disastrously.
For your dummy packages, are you referring to InsertService? I’m curious as to how you make this work with visualizing things.
I place a positioner (CAT in the image below) in Studio. The positioner is a Model, that contains a block called Positioner, and a model called Dummy. At runtime, I delete Dummy, and use Positioner as the location to place a clone of my model that I am inserting. If this doesn’t make sense, let me know.
function module.addModel(props)
local defaultOffsetConfig = {
useParentNearEdge = Vector3.new(0, 0, 0),
useChildNearEdge = Vector3.new(0, 0, 0),
offsetAdder = Vector3.new(0, 0, 0)
}
local parentFolder = props.parentFolder or workspace
local positionerModel = props.positionerModel
local templateName = props.templateName
local offsetConfig = props.offsetConfig or defaultOffsetConfig
if not positionerModel then
return
end
local dummy = Utils.getFirstDescendantByName(positionerModel, 'Dummy')
if dummy then
dummy:Destroy()
end
local positioner = positionerModel.Positioner
local cloneProps = {
parentTo = parentFolder,
positionToPart = positioner,
templateName = templateName,
fromTemplate = true,
offsetConfig = offsetConfig
}
local newItem = Utils.cloneModel(cloneProps)
return newItem
end
local newReplicator =
AddModelFromPositioner.addModel(
{
parentFolder = parentFolder,
templateName = 'LetterKeyReplicatorTemplate',
positionerModel = positionerModel,
offsetConfig = {
useParentNearEdge = Vector3.new(0, -1, 0),
useChildNearEdge = Vector3.new(0, -1, 0),
offsetAdder = Vector3.new(0, 0, 0)
}
}
)
2 Likes
Hello there, I have been experiencing this with the packages I have, it’s been happening with 2 models:
1st: It’s full of accessories, when I started changing it once, it always needs me to update it.
2nd: I think I added a viewportframe and a model inside that has bones, which is why it’s always thinking I haven’t published yet. I do not know if this still keeps happening as it only happens to me once for this 2nd type of bug.
2 Likes
I still experience it with the package full of humanoids I mentioned in the OP, so it’s totally possible. I figure it’s probably some sort of floating point error with NPC pieces and accessories.
Thank you for bringing up this issue. We are looking into it and will have a better solution to fix the modification issue in packages with humanoids.
3 Likes
Can confirm this is still happening with humanoids.
August 16, 2021.
I won’t let me undo the changes to the package, so I can’t publish the place until the package is deleted.
1 Like
Can also reconfirm. I’ve been unable to rollout an update to my game that has this humanoid package system. I can definitely make it not a package as a workaround, but it’s not ideal no matter how you slice it.
1 Like
We’ve just released a fix for the humanoid issue. Can you please retry it? Thanks!
3 Likes
Humanoids with a lot of pieces still seem to have blips of this issue, but far less frequent. Do I need to publish my packages again to receive this fix?
A singular humanoid and multiple humanoids appear to be better. You can move them using the “Select”, “Move” and “Rotate” tools with minimal issue.
Non-humanoid packages are still iffy. Eventually you can manipulate them enough to where it thinks you’ve changed it. You can resolve it by reverting the package.
Using the “Transform” tool enough eventually seems to break the changed status of any package.
1 Like
To receive the change, you will need to at least undo local changes.
For non-humanoid package, please create a new ticket for it. Please provide the minimal steps to reproduce the issue. Thanks!
3 Likes
Looks like someone may’ve beaten me to the punch for non-humanoid packages. I’ll add on to that thread.
As for this issue, there are no local changes - so the bug is still there. It’s significantly better than before though.
This bug seems to be fixed a while ago but it’s happening to me and it’s worst, I cannot publish my game because packages can’t be updated. The video takes a while but you can see that, upon publishing. It says that I did not publish the package.
Hello @APandaPoet, sorry for the late bump. I would also like to clarify what happened with me:
I had a package in StarterPlace, which has a universe / subplace of that same place. I didn’t have an issue updating my package until I tried inserting this package(which has a humanoid rig) into one of the universes and ran into the unchangeable or unpublishable issue. To be clear, this is a brand new package I made a couple of days ago (just learned about them)
Hi @grar21, thanks for sharing it! It’s very helpful for us to debug the issue.
Unfortunately I’m not on the package team anymore. I’ll forward the message to the team.
6 Likes
I’m getting this issue now within a UI tree, and it’s preventing me from making a VERY critical publish on a major game.
DM for RBXM / team create link?