BetterTC 1.6.4

also if they remove any of the sulfer or gp already in the tc, they cannot put it back. just started today, not yesterday

The Plugin lists the Umod No escape plugin as having Integration, But does the paid NoEscape plugin By Khan also Have Integration with BetterTC?

42 minutes ago, AshCrack said:

The Plugin lists the Umod No escape plugin as having Integration, But does the paid NoEscape plugin By Khan also Have Integration with BetterTC?

I haven't tested it because I don't have it, but if it uses the same hooks as the free plugin it should be compatible.

22 minutes ago, ninco90 said:

I haven't tested it because I don't have it, but if it uses the same hooks as the free plugin it should be compatible.

Alrighty Just wanted to ask Thanks!

Updating to this level is currently blocked

The upgrade is not working

2 hours ago, Ram58 said:

The upgrade is not working

Amoti kactoma! Itwero cwalo bota gin ma ki nyutu wek aniang maber ngo ma tye ka time ki kit ma tye ka gengo in kwede?

9 hours ago, ninco90 said:

Amoti kactoma! Itwero cwalo bota gin ma ki nyutu wek aniang maber ngo ma tye ka time ki kit ma tye ka gengo in kwede?

как это исправить ?

Any chance to have support with 

?

1 hour ago, Wizz said:

Any chance to have support with 

?

I don't have that plugin, but I'd say that if the plugin accepts the same hooks/APIs as the free NoEscape plugin, it should be compatible.

Do you have "Use NoEscape Plugin: true" enabled in your configuration?

@ninco90 @Wizz
The NoEscape API is publicly documented and has remained consistent without changes, so adding support is straightforward. A developer doesn't need to own or personally use the plugin to implement compatibility they simply need to follow the documented API/hooks.

Whether someone owns the plugin shouldn't determine whether they can support it. If a plugin exposes a documented API, that's exactly what it's there for. 

10 minutes ago, Khan said:

@ninco90 @Wizz
The NoEscape API is publicly documented and has remained consistent without changes, so adding support is straightforward. A developer doesn't need to own or personally use the plugin to implement compatibility they simply need to follow the documented API/hooks.

Whether someone owns the plugin shouldn't determine whether they can support it. If a plugin exposes a documented API, that's exactly what it's there for. 

Yes, I saw it, that's why I said it should be compatible. I already have this for the free plugin and it works.

Did you add the NEW DLC glow wall papers yet? https://rust.facepunch.com/store/pack/glowingwallpaperpack

I updated the the better TC to the latest version, But did not see them in the available wall papers, it is possible im blind and did not see them though.