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

Infos removed from notes? #5

Closed
The-Gig opened this issue Oct 21, 2019 · 5 comments
Closed

Infos removed from notes? #5

The-Gig opened this issue Oct 21, 2019 · 5 comments

Comments

@The-Gig
Copy link
Collaborator

The-Gig commented Oct 21, 2019

I noticed that "notes" in current gamepack, while added some useful infos, seem to lack other useful infos which were in old gamepack.

As example, these are the notes for "ammo_lightning" in old gamepack:

The amount of time it takes for an item in the team to respawn is determined by the "wait" value of the item that was picked up previously. So if one of the items in the team has it's "wait" key set to -1 (never respawn), the random respawning cycle of the teamed items will stop after that item is picked up.

When the random key is set, its value is used to calculate a minimum and a maximum delay. The final time delay will be a random value anywhere between the minimum and maximum values: (min delay = wait - random) (max delay = wait + random).

And these are the notes for the same in current gamepack:

Values for the 'gametype' and '!gametype' keys need to be separated by spaces. The valid values are the following for each gametype:

  • ffa: Free For All
  • tournament: Tournament
  • single: Single Player
  • team: Team Deathmatch
  • ctf: Capture the Flag and CTF Elimination
  • oneflag: One Flag CTF
  • obelisk: Overload
  • harvester: Harvester
  • elimination: Elimination
  • lms: Last Man Standing
  • dd: Double Domination
  • dom: Single Domination
  • pos: Possession
    Unless a specific kind of gameplay requires it or you plan to team up items, DON'T set the 'wait' or 'count' keys. You don't want to mess with your players' timing of the items or what the players expect from the items they pick up. If you want to limit an entity to make it viable on your map, rethink the layout of your map so the entity doesn't end overpowered.
    Upon activation of the targets, all shaders/textures in the map with the shader/texture mentioned in targetShaderName will change to the shader/texture mentioned in targetShaderNewName. This is useful for on/off switches, for example.

What about changing to something like:

Values for the 'gametype' and '!gametype' keys need to be separated by spaces. The valid values are the following: ffa tournament single team ctf oneflag obelisk harvester elimination lms dd dom pos

In case of "teamed" items, the respawn time depends from the "wait" of the previously picked up item. In case a teamed item has got "wait -1" (no respawn), items of the team will stop spawing after that one has been picked up.

If "random" key is set, the respawn time can be anywhere between "wait - random" and "wait + random" seconds.

Unless you are planning a specific kind of gameplay, it's advisable to do not set "wait" or "count" keys, to do not mess with what players know about items timings and effects. If you want to limit an entity to make it viable on your map, you may rethink the layout of your map so the entity doesn't end overpowered.

Upon activation of the targets, all shaders/textures in the map with the shader/texture mentioned in targetShaderName will change to the shader/texture mentioned in targetShaderNewName. This is useful for on/off switches, for example.

(Merged the two descriptions, having care to reword those from older gamepack, which probably was not fully gpl - the main reason behind the whole gamepack rewrite)

Furthermore... is it just me, or do all the entities definitions lack the explanation of their SPAWNFLAGS?

@NeonKnightOA
Copy link
Owner

Can you create a pull request by modifying the respective fields in the .csv files?

@NeonKnightOA
Copy link
Owner

Item description tackled on fd081c9.

As for spawnflags, I suppose you're talking about the .ent files. I still have no idea about how to tackle that one.

@The-Gig
Copy link
Collaborator Author

The-Gig commented Feb 3, 2020

About the spawnflags:
I haven't checked this stuff in some time. My fault. At a certain point I thought that maybe the export script is faulty when exporting to one if the two formats, so a fix of the python/anaconda script would have been needed (nothing I may be capable of). But I'm not sure about it, as I didn't complete the tests and some months passed since then...

@NeonKnightOA
Copy link
Owner

As far as I know, the problem was in the Python scripts. I guess @sago007 tried to incorporate them but haven't had the time or something like that. Can't remember now what he said.

@NeonKnightOA
Copy link
Owner

Since the note removal is already tackled, I've opened a new issue about spawnflags.

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

2 participants