😅FAQ

Frequently asked questions.

This page is an archive and features legacy versions of TouchGuild. Any information coming from it is outdated.

Why is TouchGuild in early access?

TouchGuild is deploying slowly, we tested every methods, events.. but we're sure there is hidden bugs. It's up to you to tell us the bugs, as you use the library!

If you find a bug, make sure to report it by clicking here.

When we'll see that the library is stable, we'll switch to a 'B.E.T.A' branch since the Guilded API is still in early access.

How to collaborate to the library's development?

You can make pull requests through our GitHub repository. We're enabling everyone to collaborate to your library, because it is yours.

You don't know how pull requests works? Click here.

"I don't get why I should use TouchGuild over guilded.js"

TouchGuild has a different approach about how you use a library.

While creating TouchGuild, we thought about how it should be used & how to make the library durable & even if deprecation happen.

We built TouchGuild to be durable, if deprecation happens you can still use it by importing 'DevTools' and send requests to the Guilded API, we also made proper methods to use less ram & get data that directly comes from the API itself. (those methods are called Non-REST methods)

We also built our cache to be simple but useful. The TouchGuild's cache stores message, guild & member components when message sent, so you can get information about them when you'd like, and even more. You can also get the whole cache by using 'Client.cache'.

We're making interfacing with the API accessible, and easier. Everything's related to this is gonna be managed by us. You have to build everything on your own, except the communcation layer between you & Guilded.

Is TouchGuild for beginners?

TouchGuild requires advanced development skills, the basis are understandable by beginners.

The TouchGuild library does not include helpful constructors to:

• easily make embeds

• collect messages

It still can be used for beginners if they're able to create message collectors & more, if they need to.

Why types are weird compared to other libraries?

Types are inspired of Eris & Oceanic.js (Discord libraries). Every methods, properties are named wisely to be accurate about what they're actually doing.

For example, a REST method will be named 'getRESTChannelMessages' and the Non-REST method will be named 'getChannelMessages'

More frequently asked questions coming soon, as they're asked, haha!