Package Details: forge-server 50.1.0-2

Git Clone URL: https://aur.archlinux.org/forge-server.git (read-only, click to copy)
Package Base: forge-server
Description: Forge is a free, open-source modding API all of your favourite mods use!
Upstream URL: https://minecraftforge.net
Keywords: forge minecraft mod
Licenses: custom
Provides: forge-server
Submitter: thisischrys
Maintainer: NukeCode87
Last Packager: NukeCode87
Votes: 2
Popularity: 0.000000
First Submitted: 2021-03-07 07:18 (UTC)
Last Updated: 2024-11-22 16:04 (UTC)

Latest Comments

1 2 Next › Last »

NukeCode87 commented on 2024-12-30 23:55 (UTC)

You are correct @tupiasplyths, the forged command was a renamed version of this repository: https://github.com/Edenhofer/minecraft-server. I have removed this as a dependency in order reduce complexity and get this repository working again. You can start the server as a service via 'sudo systemctl start forge-server' or you can start it in the foreground by launching the jar file here: /opt/forge-server/forge-server.jar.

tupiasplyths commented on 2024-12-30 04:18 (UTC)

Am I dumb or forged disappeared?

NukeCode87 commented on 2024-11-20 15:46 (UTC) (edited on 2024-11-20 15:46 (UTC) by NukeCode87)

Hi, I've decided to adopt this package and simplify it. Let me know if you run into any issues.

Swiftloke commented on 2024-05-28 01:47 (UTC)

This package appears to be broken.

Here is the result of starting the server with a fresh installation:

$ forged start
Starting server... failed

exec java @/srv/forge/libraries/net/minecraftforge/forge/1.20.4-49.0.27/user_jvm_args.txt @/srv/forge/libraries/net/minecraftforge/forge/1.20.4-49.0.27/unix_args.txt
Error: Unable to access jarfile forge-1.20.4-49.0.27-shim.jar
no server running on /tmp/tmux-964/forge

oritwoen commented on 2024-05-09 10:41 (UTC) (edited on 2024-05-09 10:47 (UTC) by oritwoen)

An orphan announcement has been posted for this package.

Unfortunately, despite my great intentions, I was unable to find enough time to manage it and was unable to deal with it properly. I hope the next person who takes it over will be able to take good care of it.

For the new packager: request to unpin my old comments.

oritwoen commented on 2024-02-08 21:27 (UTC)

I started updates in the GitHub repository. You can see changes there on an ongoing basis. Once I test everything under the latest versions, I will upload updates to the AUR.

Sorry for such a long wait!

Repository: https://github.com/oad-earth/mina

duckdalbe commented on 2023-10-09 16:29 (UTC)

I have similar but different problem as the last poster.

After installing, starting the server fails with the message "can't find window: 0". This appears to come from tmux.

Repeatedly calling forged start result in in this error message: "Starting server...duplicate session: forge", which also appears to be a message from tmux.

Fiddling around I found that adding the following as new line 182 helps this concrete problem:

    ${SUDO_CMD} tmux -L "${SESSION_NAME}" new-window -t "${SESSION_NAME}":0

trainzkid commented on 2023-08-07 00:22 (UTC)

Found another issue, sorry! Looks like something weird happens when forged.service is asked to stop:

Stopping forge Server...
Server is going down... timed out
forged.service: State 'final-sigterm' timed out. Killing.
forged.service: Killing process 3842381 (java) with signal SIGKILL.
forged.service: Killing process 3842409 (C2 CompilerThre) with signal SIGKILL.
forged.service: Killing process 3842458 (GC Thread#4) with signal SIGKILL.
forged.service: Killing process 3842459 (GC Thread#5) with signal SIGKILL.
forged.service: Killing process 3842460 (GC Thread#6) with signal SIGKILL.
forged.service: Killing process 3842462 (GC Thread#8) with signal SIGKILL.
forged.service: Killing process 3842463 (GC Thread#9) with signal SIGKILL.
forged.service: Killing process 3842464 (n/a) with signal SIGKILL.
forged.service: Killing process 3842465 (GC Thread#11) with signal SIGKILL.
forged.service: Killing process 3842679 (n/a) with signal SIGKILL.
forged.service: Killing process 3842680 (FileSystemWatch) with signal SIGKILL.
forged.service: Killing process 3842698 (GC Thread#12) with signal SIGKILL.
forged.service: Killing process 3842699 (n/a) with signal SIGKILL.
forged.service: Killing process 3842700 (G1 Conc#2) with signal SIGKILL.
forged.service: Killing process 3842701 (G1 Conc#3) with signal SIGKILL.
forged.service: Killing process 3842702 (n/a) with signal SIGKILL.
forged.service: Killing process 3842729 (n/a) with signal SIGKILL.
forged.service: Killing process 3842730 (n/a) with signal SIGKILL.
forged.service: Killing process 3842731 (n/a) with signal SIGKILL.
forged.service: Killing process 3842748 (n/a) with signal SIGKILL.
forged.service: Killing process 3842767 (n/a) with signal SIGKILL.
forged.service: Killing process 3842916 (n/a) with signal SIGKILL.
forged.service: Killing process 3842998 (n/a) with signal SIGKILL.
forged.service: Killing process 3842999 (n/a) with signal SIGKILL.
forged.service: Killing process 3843001 (n/a) with signal SIGKILL.
forged.service: Killing process 3843003 (n/a) with signal SIGKILL.
forged.service: Killing process 3843008 (n/a) with signal SIGKILL.
forged.service: Killing process 3843010 (n/a) with signal SIGKILL.
forged.service: Killing process 3843013 (n/a) with signal SIGKILL.
forged.service: Killing process 3843014 (n/a) with signal SIGKILL.
forged.service: Killing process 3843016 (n/a) with signal SIGKILL.
forged.service: Killing process 3843017 (n/a) with signal SIGKILL.
forged.service: Killing process 3843019 (n/a) with signal SIGKILL.
forged.service: Killing process 3843020 (n/a) with signal SIGKILL.
forged.service: Killing process 3843021 (n/a) with signal SIGKILL.
forged.service: Killing process 3843110 (n/a) with signal SIGKILL.
forged.service: Killing process 3843133 (n/a) with signal SIGKILL.
forged.service: Killing process 3843134 (n/a) with signal SIGKILL.
forged.service: Killing process 3848247 (n/a) with signal SIGKILL.
forged.service: Killing process 3849320 (n/a) with signal SIGKILL.
forged.service: Killing process 3849437 (n/a) with signal SIGKILL.
forged.service: Killing process 3850404 (n/a) with signal SIGKILL.
forged.service: Killing process 3850430 (n/a) with signal SIGKILL.
forged.service: Killing process 3850457 (n/a) with signal SIGKILL.
forged.service: Killing process 3850459 (n/a) with signal SIGKILL.
forged.service: Killing process 3850460 (n/a) with signal SIGKILL.
forged.service: Killing process 3850461 (n/a) with signal SIGKILL.
forged.service: Killing process 3850462 (n/a) with signal SIGKILL.
forged.service: Killing process 3850463 (n/a) with signal SIGKILL.
forged.service: Killing process 3850464 (n/a) with signal SIGKILL.
forged.service: Killing process 3850465 (n/a) with signal SIGKILL.
forged.service: Killing process 3850466 (n/a) with signal SIGKILL.
forged.service: Killing process 3850467 (n/a) with signal SIGKILL.
forged.service: Killing process 3850468 (n/a) with signal SIGKILL.
forged.service: Killing process 3850469 (n/a) with signal SIGKILL.
forged.service: Killing process 3850477 (IO-Worker-46) with signal SIGKILL.
forged.service: Killing process 3851148 (n/a) with signal SIGKILL.
forged.service: Killing process 3851375 (n/a) with signal SIGKILL.
forged.service: Killing process 3851788 (n/a) with signal SIGKILL.
forged.service: Killing process 3851792 (n/a) with signal SIGKILL.
forged.service: Killing process 3851794 (n/a) with signal SIGKILL.
forged.service: Killing process 3851800 (n/a) with signal SIGKILL.
forged.service: Failed with result 'timeout'.
Stopped forge Server.
forged.service: Triggering OnFailure= dependencies.
forged.service: Consumed 3min 42.592s CPU time.

I've got services set to notify on failure, so this notifies me each time the service is stopped, which isn't great, and if it's failing, that indicates something is wrong.

I also haven't figured out how to connect to the tmux session to send commands to the server. When I tmux list-sessions as the forge user, it errors with error connecting to /tmp/tmux-940/default (No such file or directory), even though that directory DOES exist.

~> exa /tmp/tmux-940/
default  forge
~> exa --long /tmp/tmux-940/default 
srw-rw---- 0 forge  6 Aug 18:59 /tmp/tmux-940/default

Thank you for taking a look!

oritwoen commented on 2023-08-02 10:20 (UTC)

@trainzkid Thanks for reporting and waiting! I will update and improve all packages and create a repository :)

trainzkid commented on 2023-08-02 10:17 (UTC) (edited on 2023-08-02 10:18 (UTC) by trainzkid)

Error during install:

error: unable to run hook forge-mods.hook: could not satisfy dependencies

(5/6) Restart the forge world.                         
Job for forged.service failed because the control process exited with error code.                                      
See "systemctl status forged.service" and "journalctl -xeu forged.service" for details.                               
error: command failed to execute correctly

[10:02:12] [main/WARN] [minecraft/Eula]: Failed to load eula.txt                                                      
[10:02:12] [main/INFO] [minecraft/Main]: You need to agree to the EULA in order to run the server. Go to eula.txt for more info.                                                                                                            
no server running on /tmp/tmux-940/forge                   
forged.service: Control process exited, code=exited, status=1/FAILURE                                                 
forged.service: Failed with result 'exit-code'.
Failed to start forge Server.

I'm aware that I need to accept the eula first, but this is a fresh install. Why is it trying to restart a freshly installed server? I don't believe minecraft-server (which this PKG is based on, afaik?) causes a failed service on fresh install. What does this PKG do differently that causes that, and what could be changed so that it doesn't? Pardon my ignorance.

1 2 Next › Last »