Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Default blaster removed? Also g_forcepowerdisable inconsistent from vanilla #129

Open
AgitationSkeleton opened this issue Mar 16, 2024 · 0 comments

Comments

@AgitationSkeleton
Copy link

Reporting a bug? Please make sure you've given the following information in detail - thanks!

Operating system and version:
Windows 10, most recent build of EternalJK at time of writing

Description of the bug (and if possible, steps to reproduce the bug):
Run server with following settings:

`set g_gametype 0

seta sv_maxclients 16
seta g_inactivity 0
sv_maxRate 10000
set g_allowvote
set mtimelimit 0
seta fraglimit 0
set capturelimit 20
set g_autoMapCycle 1

g_maxForceRank 8
g_forcepowerdisable 32765
g_forceregentime

map ffa_bespin

kick allbots
bot_minplayers 3

status`

The default blaster (the Han Solo-looking one, the JK3 version of the Bryar Blaster) does not spawn in the player's inventory, leaving only lightsaber/fists (depending on force power). Also, these force power settings, which in vanilla restrict to just jump and saber-related powers, do not apply the same restrictions, or any at all, in EternalJK.

What did you expect to happen instead?
I would like players to spawn with the default blaster and for the force power restrictions I use for vanilla to work. For now I will be switching back to OpenJK for hosting since this appears to just be an EternalJK thing, which I switched to hoping it would make my server appear in the master list, which it also did not.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant