Feature request: disable gate types dialing eachother or increase power costs between them

[ghost]

Because i'm implementing a "stargate" themed multiverse multiplayer server, it would be really helpful to either increase inter-gate-type dialing power costs (via config) or disable it completely (via config on/off switch)

That way I can use worldguard or other plugins to restrict gate type construction to the correct worlds - therefore simulating galaxies (And I could make midway able to function as a midway station!)

As far as priority goes if the devs agreed to this, it's not that important, but would be kind of cool to see in action.

Preferred would be the increase in power costs config option =D

[JohnOptegrove]

Interdimensional gate power costs being raised makes more sense than simply between different gate designs. After all, with the exception of the Destiny gates, all of them have the same basic construction and features.

[ghost]

This is an aethstheic feature.

and in the series gates were galaxy specific to the point where they had to be completely recalibrated for use elsewhere - and the Pegasus gates prevented Milky Way ones from functioning in the same area also.

As per my request it would only be an option for people to use though.

[ghost]

I'm trying to Learn java now lol

[DrakeBD]

If memory serves me correctly been a while since I seen atlantis the team dialled from earths milky way gate to the atlantis Pegasus gate and through the series visa versa.

So suppose it is possible with the 8 and 9 chevron addresses for all gates to contect to each other

[mginn]

Going off of Atlantis. All Pegasus gates "could" dial Milky Way but they needed the special control crystal from Atlantis's gate. That would seem like a hassle however for the mod so I am content just watching the development as is.

[JohnOptegrove]

The Pegasus gates don't even animate correctly right now, so I think overriding Milky Way gates in the vicinity should probably wait a while.

Besides, if we go strictly from canon, only one gate per dimension should work at all, let alone per chunk.

[ghost]

@mginn is correct.

Still, this was optional so I could simulate the stargate universe a little better on my server. We'll see what happens haha

[AfterLifeLochie]

I would like to avoid prioritizing types of gates and gate priorities, because this requires me to do nasty things on the server responsible. Even though it's a nice concept, I would have to scan the entire chunk and generate a list of gates -- right now the code scans for the first available gate and ignores any others which may also be valid.

I also understand why you would want to increase costs between gate types, but it personally doesn't make much sense. You can now increase the cost to change dimensions and the costs associated with dialling initially, so the use-case for this feature is really limited to server environments.

[AfterLifeLochie]

No, I'm not closing the issue -- I just do not understand what the scope of your use-case for this feature is.

I'm about to start exposing more things through APIs which other mods can interact with - including access to connection management - so I'd much rather avoid adding features for very specific use cases. If many servers and players want to restrict which gates can be dialled I can add the feature directly - if not, you could always write a FML mod (or a Bukkit plugin, if you're using Cauldron).

For your multiverse server, you can already restrict the types of gates which can be placed - based on metadata. In fact, it is only possible to legitimately craft the standard Stargate types, and all other gate types are strictly experimental at this stage -- the only reason they are not disabled as per your request in issue #214 is because I cannot disable specific types of gates without disabling gates altogether.

I have also already implemented the distance-energy cost you requested in issue #91. Is this not suitable for your use case?

[ghost]

The idea is to be able to simulate a galaxy based environment - Multiple to be exact. As the whole idea of my SMP server is to be builds from the Stargate Universe.

That way I can restrict travel between World Group 1 (Milky way) and World Group 2 (Pegasus) and World Group 3 (Destiny/SGU worlds) to those who have completed the correct roleplay, or those who can generate that much energy.

The idea is you have this at present:

distanceModifier (same world) dimensionModifier (across worlds)

I'm proposing you add:

gateTypeModifier (across Galaxies or "world groups")

and optionally:

disableInterGateTypeDialing = true/false

World groups would be handled via an external plugin (such as WorldGuard) or mod to restrict creation of Milky way gates in worlds deemed to be part of pegasus by admins , and the reverse would occur, forcing additional power to be used when gating between them.

For those who don't want to use the config option they could just leave it set to 1.0 or something.

The guys working with me at present really are keen on adding a bit of roleplay content and progression to the server - this would help immensely, but I understand it isnt a priority for you and is really quite trivial :)

When you think about it, at present the gate types are really just skins though - This would give them a purpose?

Sorry If i'm difficult to communicate with haha.

[AfterLifeLochie]

Different gate types are skins at the moment, primarily because their rendering hasn't been replaced as of yet. Please see my response regarding role-playing features on issue #223.

[JohnOptegrove]

This still makes absolutely no sense. In the series it didn't take an exorbitant amount of energy to dial to other galaxies because of the different gates, it was because of the ridiculous distance between galaxies. The gate design is fundamentally identical - there's no real reason why it would cost more energy. By that logic, the SGC shouldn't have been able to dial into, say, the Tollan stargate, without using a ZPM or other energy source.

[ghost]

Worldguard and no-construction are the only way to simulate the distance your speaking of.

And as for the people who complain about the feature request with every "slightly out there request" ive ever done, I've also specified and explained how to make it an optional feature, so people like @JohnOptegrove can stop complaining.

I work as a sysadmin for a web development shop. Keeping Developers happy, bosses happy and clients happy is my job and you should bother to read what I post before you respond.

[ghost]

@AfterLifeLochie So you're closing the issue? We've wasted all this time talking when it was a no from the get go? (and when I asked before) slaps forehead lol