Jump to content

"incomplete set of tags" and/or mods not being loaded server side

Recommended Posts

First things first: LOGS, CLIENT AND SERVER and my MODS boom, done

Second things second: This is running on a 4GB RASPBERRY PI 4 with the files are transfered to it using SCP IN WINDOWS command prompt such as MODS AND THE LATEST 1.16.4 FORGE INSTALLER 


Now onto the main content: Every time I try to load in with mods enabled I get the "incomplete set of tags" warning and get kicked back to the server list. However when I do not load any mods im fully able to get in the server and its running perfectly. I have also tried (over a long period of literally three to four DAYS of waiting for boot ups and shut downs of both game and server) loading up each mod individually none of which work, either im very very unlucky with my choices or mods arent being initialised on the server side. I have done a lot of extensive googling on both pussible issues and have come up with little to nothing that has been useful to me.


EDIT: i dont know if this matters but i followed this guide which suggests:

"Finally, forge-1.16.4.jar is the file we’ll use to start the server. I like to copy this file with a new name to make things easier.

cp forge-1.16.4.jar startup.jar

This will make a new file called forge.jar that we can use instead. Totally optional."

which I did to make it easier to boot the server when the pi boots


Thanks in advance for any and all help you guys can provide

Edited by pandaman144
Link to comment
Share on other sites

Please provide debug.log for both client and server

This is my Forum Signature, I am currently attempting to transform it into a small guide for fixing easier issues using spoiler blocks to keep things tidy.


As the most common issue I feel I should put this outside the main bulk:

The only official source for Forge is https://files.minecraftforge.net, and the only site I trust for getting mods is CurseForge.

If you use any site other than these, please take a look at the StopModReposts project and install their browser extension, I would also advise running a virus scan.


For players asking for assistance with Forge please expand the spoiler below and read the appropriate section(s) in its/their entirety.


Logs (Most issues require logs to diagnose):


Please post logs using one of the following sites (Thank you Lumber Wizard for the list):

https://gist.github.com/100MB Requires member (Free)

https://pastebin.com/: 512KB as guest, 10MB as Pro ($$$)

https://hastebin.com/: 400KB

Do NOT use sites like Mediafire, Dropbox, OneDrive, Google Drive, or a site that has a countdown before offering downloads.


What to provide:

...for Crashes and Runtime issues:

Minecraft 1.14.4 and newer:

Post debug.log

Older versions:

Please update...


...for Installer Issues:

Post your installer log, found in the same place you ran the installer

This log will be called either installer.log or named the same as the installer but with .log on the end

Note for Windows users:

Windows hides file extensions by default so the installer may appear without the .jar extension then when the .log is added the log will appear with the .jar extension


Where to get it:

Mojang Launcher: When using the Mojang launcher debug.log is found in .minecraft\logs.


Curse/Overwolf: If you are using the Curse Launcher, their configurations break Forge's log settings, fortunately there is an easier workaround than I originally thought, this works even with Curse's installation of the Minecraft launcher as long as it is not launched THROUGH Twitch:

  1. Make sure you have the correct version of Forge installed (some packs are heavily dependent on one specific build of Forge)
  2. Make a launcher profile targeting this version of Forge.
  3. Set the launcher profile's GameDir property to the pack's instance folder (not the instances folder, the folder that has the pack's name on it).
  4. Now launch the pack through that profile and follow the "Mojang Launcher" instructions above.






or alternately, 


Fallback ("No logs are generated"):

If you don't see logs generated in the usual place, provide the launcher_log.txt from .minecraft


Server Not Starting:


If your server does not start or a command window appears and immediately goes away, run the jar manually and provide the output.


Reporting Illegal/Inappropriate Adfocus Ads:


Get a screenshot of the URL bar or copy/paste the whole URL into a thread on the General Discussion board with a description of the Ad.

Lex will need the Ad ID contained in that URL to report it to Adfocus' support team.


Posting your mod as a GitHub Repo:


When you have an issue with your mod the most helpful thing you can do when asking for help is to provide your code to those helping you. The most convenient way to do this is via GitHub or another source control hub.

When setting up a GitHub Repo it might seem easy to just upload everything, however this method has the potential for mistakes that could lead to trouble later on, it is recommended to use a Git client or to get comfortable with the Git command line. The following instructions will use the Git Command Line and as such they assume you already have it installed and that you have created a repository.


  1. Open a command prompt (CMD, Powershell, Terminal, etc).
  2. Navigate to the folder you extracted Forge’s MDK to (the one that had all the licenses in).
  3. Run the following commands:
    1. git init
    2. git remote add origin [Your Repository's URL]
      • In the case of GitHub it should look like: https://GitHub.com/[Your Username]/[Repo Name].git
    3. git fetch
    4. git checkout --track origin/master
    5. git stage *
    6. git commit -m "[Your commit message]"
    7. git push
  4. Navigate to GitHub and you should now see most of the files.
    • note that it is intentional that some are not synced with GitHub and this is done with the (hidden) .gitignore file that Forge’s MDK has provided (hence the strictness on which folder git init is run from)
  5. Now you can share your GitHub link with those who you are asking for help.

[Workaround line, please ignore]


Link to comment
Share on other sites

1 hour ago, diesieben07 said:

You are starting a vanilla server.

thanks. but rather than leaving it there with no further information, mind telling me how i can make the server start with mods or at least direct me to some reliable sites that tell me how? blunt answers arent helpful to me (and quite surprising that its coming from a moderator -_-)

Edited by pandaman144
Link to comment
Share on other sites

1 minute ago, diesieben07 said:

The forge installer does not generate any file called "startup.jar" so you didn't follow at least one of the instructions.

startup.jar is a cp of the forge loader, renamed to make it easier to run on boot when the pi starts up, other than that it is an entirely forge install and i still have the forge loader, my fault for not clarifying ill add it to my post

Link to comment
Share on other sites

8 hours ago, diesieben07 said:

Well, the server log you posted suggested that is not what you did, because that is a vanilla log, not a forge log.

Look. I get you're a forum moderator and you probably deal with stuff like this too much. But, when I say "I did X" dont make your responce be "well clearly you didn't do X."

heres the server files

heres the mods on the server 

Go through them youll notice that every mod matches my client side mod list

Link to comment
Share on other sites

8 minutes ago, diesieben07 said:

If you want me to lie to you so it makes you feel better... then we can end this right here because it's not helpful.

This log is a VANILLA LOG. The latest server.debug.log you now posted (here) is actually a forge log. Notice how it actually mentions forge starting up as opposed to the vanilla log you posted? Okay.

Now, the client log you posted shows the modded client trying to connect to a vanilla server and therefor failing. These two logs match up in terms of timestamps.

The forge log you now posted has completely different timestamps so the client log you originally posted took place at a completely different time of day and therefor the two do not belong to each other.

Your statement that a debug.log is only created in case of a crash is factually incorrect. Please post the client's debug.log trying to connect to the forge server.

okay, my mistake about the client debug log. HOWEVER a debug.log was not created in the clientside folder. even when i tested it RIGHT NOW and got the same error. no debug.log see?

Link to comment
Share on other sites

17 minutes ago, diesieben07 said:

DaemonUmbra's signature has a special section for how to obtain the debug.log on the curse launcher, because the curse launcher is a broken piece of *** and still breaks the debug.log.

You can post the latest.log instead, it might be enough.

sorry that took a sec, had booted minecraft accidentally inbetween and caused latest.log to be like, 5 lines. here's a latest.log that shows the missing tags error

Link to comment
Share on other sites

1 minute ago, diesieben07 said:

Then I don't know what to tell you. Either you are not launching the server correctly or you are posting the wrong client log.

ugh irdk anymore. know any really good detailed guides i can follow? every guide is like "heres all the commands, wanna add mods? make a folder. got problems? tough shit"

Link to comment
Share on other sites

Just now, diesieben07 said:

Well, it's literally as simple as that. You run the installer, you make a mods folder, you start the forge jar. Done.

i know, and ive done it before and had it work fine. but moving from pi 3 to pi 4 seems to have ruined it, i even fresh installed raspbian and everything

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Create New...

Important Information

By using this site, you agree to our Terms of Use.