You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 1, 2021. It is now read-only.
Hi,
sorry to bother you, but I like your mod, however it somehow fails to work for me. Both on server & client only , dummy denies to be placed on creative and also on survival. On survival it eats the item, but nothing shows. Was unable to summon the dummy into the world at all...
Even tried to do /summon testdummy.Dummy , what written "Object succesfully summoned", however nothing showed...
Logs are empty, no error, nothing....
Do you have anz idea, what can be going on? I'm using Forge 1492 (1.7.10). Installation seems to be good, both on server and client...
Can probably update something in it myself, however i'm just coder begginer and really don't see the error in this.
Thanks
The text was updated successfully, but these errors were encountered:
Also getting a similar issue. Appears to be some sort of problem with Mob Properties.
Testing in SSP, Forge ver 1558, Mmm ver 1.9, Mob Properties ver 0.4.3
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi,
sorry to bother you, but I like your mod, however it somehow fails to work for me. Both on server & client only , dummy denies to be placed on creative and also on survival. On survival it eats the item, but nothing shows. Was unable to summon the dummy into the world at all...
Even tried to do /summon testdummy.Dummy , what written "Object succesfully summoned", however nothing showed...
Logs are empty, no error, nothing....
Do you have anz idea, what can be going on? I'm using Forge 1492 (1.7.10). Installation seems to be good, both on server and client...
Can probably update something in it myself, however i'm just coder begginer and really don't see the error in this.
Thanks
The text was updated successfully, but these errors were encountered: