Giter Site home page Giter Site logo

Comments (7)

Totenfluch avatar Totenfluch commented on August 19, 2024

autoexecconfig.txt

from eventitemsspawner.

Sacricx avatar Sacricx commented on August 19, 2024

Thank you very much for providing the autoexecconfig.txt !
Since I can only guess where to put this in, I tried all diffrent folders in addons/sourcemod/scripting/
also in addons/sourcemod/. But no matter where I put the autoexecconfig.txt the error shows up on compile. I would appreciate very much, if you could tell me/people who want to know, where to put this cfg. That would be cool :) !

best regards

Sacricx

from eventitemsspawner.

Totenfluch avatar Totenfluch commented on August 19, 2024

rename it to autoexecconfig.inc

and it's /scripting/includes

from eventitemsspawner.

Sacricx avatar Sacricx commented on August 19, 2024

Although this issue is closed already I want to share my solution of how to compile with Sourcemod 1.10 since adding the autoexecconfig.inc was just the first step which was neccessary to be able compile the plugin.

  1. You need to add smlib but download the traditional syntax branch since the master branch uses deprecated syntax and won't let you compile against SM 1.10.

  2. Adding smlib: Open your smlib-transitional_syntax.zip. Go inside the smlib-transitional_syntax folder and drag and drop the scripting folder to your servers addons/sourcemod/scripting folder

DOWNLOAD HERE: https://github.com/bcserv/smlib/tree/transitional_syntax

  1. Make sure to add: emitsoundany.inc, map_workshop_functions.inc, multicolors.inc, colors.inc, morecolors.inc store.inc to your include folder.

DOWNLOAD HERE:

  1. Edit store.inc

REMOVE THE COMPLETE LINES:

  • String:szName[ITEM_NAME_LENGTH], (Line 24)
  • iPrice, (Line 28)
  • iId, (Line 55)

The plugin should compile successfully with 6 warnings which you can ignore for now.
I hope this detailed solution and report helps someone who wants to compile against SM 1.10.

  1. To Totenfluch:

This warnings are related but can be ignored until SM 1.11 I guess:

  • addons\sourcemod\scripting\EventItemsSpawner.sp(32) : warning 241: Array-based enum structs will be removed in 1.11.
    See https://wiki.alliedmods.net/SourcePawn_Transitional_Syntax#Enum_Structs

  • addons\sourcemod\scripting\EventItemsSpawner.sp(278) : warning 213: tag mismatch

  • addons\sourcemod\scripting\EventItemsSpawner.sp(6) : warning 203: symbol is never used: "g_cvarChatTag"

from eventitemsspawner.

Totenfluch avatar Totenfluch commented on August 19, 2024

You are basically describing how to compile the plugin. This does not seem to be an issue with 1.10 in particular just you having to go through the though process of compiling this. I could have done a better job documenting this bu that's why there's a .smx in the directory.

about the 1.11 yes I agree this is problematic but since the whole plugin relies on enum-structs this will be a though one to migrate

from eventitemsspawner.

Totenfluch avatar Totenfluch commented on August 19, 2024

b8eccbf

from eventitemsspawner.

Sacricx avatar Sacricx commented on August 19, 2024

You are right its no issue with SM 1.10. Without the include files you can't compile it against SM 1.9 either. That was not necessary for me in the past tho since the provided .smx in the directory worked well for me with SM 1.9. Because of that I did never try to recompile with SM 1.9 and thought it's been an issue with SM 1.10.

Unfortunatley the provided .smx doesn't work with SM 1.10 even when the cfg's are set properly
(no errorlogs tho). That's why I wanted to recompile the .sp file. Once I looked at the errors, I got rid of them step by step. And yes I could have made this alot easier by requesting you to add all the necessary include files but to edit the store.inc before.

The whole reason for my issue was simply that some plugins I'm using require SM 1.10 meanwhile which forced me to update to SM 1.10. But your plugin is so nice that I didn't want to miss it on my servers <3

Yeah and since I had no guarantee, that you come back to this issue at anytime in the future I wanted to make sure to let people know about my "solution" to this and described for them how to be able to compile against SM 1.10.

I do appreciate your reply very much and want to say that its still nowadays an awesome plugin for my Community. It was a really great idea from you to invent it and we don't want to miss it on our servers.

So long story short, thank you very much for adding the required include files to the master branch.

I wish you a good time mate :) !

Sacricx

from eventitemsspawner.

Related Issues (3)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.