Discord Hal is a user on Enjin as well. This means we can pass him admin on our sites, and use User.login to access some of the admin functions (ie ticket reporting).
Enjin API Discord Bot - I made one command thus far to get a series of users (up to 20) based on a tag. In this case, the latest users are connected to a tag and thus are spit out when I request it from the bot.
Super cool! Having a discord bot connected to Enjin would be extremely useful! Once you've finished dabbling with this, could it possibly be a public tutorial in the future?
I think the only possibility would be for me to make some public bot, someone adds HAL to their site and HAL can perform certain tasks. HAL is still very new right now though, you never know.
Thanks for the shoutout guys - Your site design was successful because of the community you already built (races, lore, the server, the logo branding etc etc) - Keep at it, hope this bring you some more attention (you deserve it). WolvesEthereal BTW I updated your profile pages to mobile a few weeks back when I converted many of my clients' profiles / dash to mobile (still doing this)
Finally updated atslayer.com, took 100 years, but the base foundation is now there - I can finally freely make some cool applications without the shackles of my previous gestapo host.
- HTTPS
- Cloudflare
- VPS from the ground up
Finally migrated atslayer.enjin.com to HTTPS, the only thing that was stopping me was that http iframe....
FYI to any Enjin website developers using the AJAX endpoint (ajax.php functions) in their code - I have a confirmation from Enjin that they officially do not support the use of it. At any point your code could be disabled (especially with admin-related or write functions).
You have a responsibility to go back and update your clients' sites with a solution as a patch will come eventually.
I for one will be going back and updating those like buttons to harvest the #enjin-like-site again, although I will request that the Site methods be allowed with a login cookie.
The login API being brought back is the big one - Using the session over the API key is a must for ANY write operation (i.e points, tags). Although we have those operations available to us now, and they actually work quite well, we obviously can't use them without the chance of exploit.
oh it's being brought back? That's great news, the session ID is required for a lot of the methods and, optimally, should be supplied to every request.
That flash of the Enjin Bar is when the #enjin-bar loads before your CSS in your HTML module. To prevent that from happening, add the #enjin-bar{display:none !important;} CSS to your header CODE INJECTION instead.
Arcade Fire - Creature Comfort (Official Video) Listen on Spotify http://smarturl.it/ArcadeFire/spotify?IQid=yt Listen on Apple Music http://smarturl.it/ArcadeFire/applemusic?IQid=yt Amazon: http://smarturl.it/ArcadeFire/az?IQid=yt Arcade Fire Store: http
I do not depend on unsupported methods in my threads (or projects), there is always a risk that the ajax.php methods will be blocked or changed. If I do use the ajax.php methods, it is in a minimal capacity.
WolvesEthereal BTW I updated your profile pages to mobile a few weeks back when I converted many of my clients' profiles / dash to mobile (still doing this) 
